You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 21, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: 052_Mapping_Analysis/30_Exact_vs_full_text.asciidoc
+4-3
Original file line number
Diff line number
Diff line change
@@ -11,15 +11,16 @@ The exact value `2014` is not the same as the exact value `2014-09-15`.
11
11
_Full text_, on the other hand, refers ((("full text")))to textual data--usually written in
12
12
some human language -- like the text of a tweet or the body of an email.
13
13
14
-
15
-
NOTE: Full text is often referred to as _unstructured data_, which is a misnomer--natural language is highly structured. The problem is that the rules of
14
+
[NOTE]
15
+
====
16
+
Full text is often referred to as _unstructured data_, which is a misnomer--natural language is highly structured. The problem is that the rules of
16
17
natural languages are complex, which makes them difficult for computers to
17
18
parse correctly. For instance, consider this sentence:
18
19
19
20
May is fun but June bores me.
20
21
21
22
Does it refer to months or to people?
22
-
23
+
====
23
24
24
25
Exact values are easy to query. The decision is binary; a value either
25
26
matches the query, or it doesn't. This kind of query is easy to express with
0 commit comments