File tree 2 files changed +14
-3
lines changed
2 files changed +14
-3
lines changed Original file line number Diff line number Diff line change @@ -7,7 +7,8 @@ produces a single token.
7
7
8
8
The `normalizer` is applied prior to indexing the keyword, as well as at
9
9
search-time when the `keyword` field is searched via a query parser such as
10
- the <<query-dsl-match-query,`match`>> query.
10
+ the <<query-dsl-match-query,`match`>> query or via a term level query
11
+ such as the <<query-dsl-term-query,`term`>> query.
11
12
12
13
[source,js]
13
14
--------------------------------
@@ -53,6 +54,15 @@ PUT index/_doc/3
53
54
54
55
POST index/_refresh
55
56
57
+ GET index/_search
58
+ {
59
+ "query": {
60
+ "term": {
61
+ "foo": "BAR"
62
+ }
63
+ }
64
+ }
65
+
56
66
GET index/_search
57
67
{
58
68
"query": {
@@ -64,7 +74,7 @@ GET index/_search
64
74
--------------------------------
65
75
// CONSOLE
66
76
67
- The above query matches documents 1 and 2 since `BÀR` is converted to `bar` at
77
+ The above queries match documents 1 and 2 since `BÀR` is converted to `bar` at
68
78
both index and query time.
69
79
70
80
[source,js]
Original file line number Diff line number Diff line change 3
3
4
4
While the <<full-text-queries,full text queries>> will analyze the query
5
5
string before executing, the _term-level queries_ operate on the exact terms
6
- that are stored in the inverted index.
6
+ that are stored in the inverted index, and will normalize terms before executing
7
+ only for <<keyword,`keyword`>> fields with <<normalizer,`normalizer`>> property.
7
8
8
9
These queries are usually used for structured data like numbers, dates, and
9
10
enums, rather than full text fields. Alternatively, they allow you to craft
You can’t perform that action at this time.
0 commit comments