Skip to content

Clarifies how the query_string splits textual part to build a query #28798

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 1, 2018
Merged

Clarifies how the query_string splits textual part to build a query #28798

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
39a9251
Clarifies how the query_string splits textual part to build a query
jimczi Feb 23, 2018
f389253
address review
jimczi Feb 28, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions docs/reference/query-dsl/query-string-query.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,14 +28,22 @@ GET /_search
"query": {
"query_string" : {
"default_field" : "content",
"query" : "field:new york AND city"
"query" : "(new york city) OR (big apple)"
}
}
}
--------------------------------------------------
// CONSOLE

... will be splitted in `new`, `york` and `city` and each part is analyzed independently.
... will be split into `new york city` and `big apple` and each part is then
analyzed independently by the analyzer configured for the field.

WARNING: Whitespaces are not considered operators, this means that `new york city`
will be passed "as is" to the analyzer configured for the field. If the field is a `keyword`
field the analyzer will create a single term `new york city` and the query builder will
use this term in the query. If you want to query each term separately you need to add explicit
operators around the terms (e.g. `new AND york AND city`).

When multiple fields are provided it is also possible to modify how the different
field queries are combined inside each textual part using the `type` parameter.
The possible modes are described <<multi-match-types, here>> and the default is `best_fields`.
Expand Down