[Docs]: Clarify query_string parser splits on operator

This commit is contained in:
Jim Ferenczi 2017-07-24 18:35:19 +02:00
parent 17714acb9e
commit 4a9995145c
4 changed files with 6 additions and 6 deletions
core/src/main/java/org/elasticsearch/index
docs/reference
migration/migrate_6_0
query-dsl

View File

@ -98,7 +98,7 @@ public class QueryStringQueryBuilder extends AbstractQueryBuilder<QueryStringQue
.withAllDeprecated("Decision is now made by the analyzer"); .withAllDeprecated("Decision is now made by the analyzer");
private static final ParseField TIME_ZONE_FIELD = new ParseField("time_zone"); private static final ParseField TIME_ZONE_FIELD = new ParseField("time_zone");
private static final ParseField SPLIT_ON_WHITESPACE = new ParseField("split_on_whitespace") private static final ParseField SPLIT_ON_WHITESPACE = new ParseField("split_on_whitespace")
.withAllDeprecated("This setting is ignored, the parser always splits on logical operator"); .withAllDeprecated("This setting is ignored, the parser always splits on operator");
private static final ParseField ALL_FIELDS_FIELD = new ParseField("all_fields") private static final ParseField ALL_FIELDS_FIELD = new ParseField("all_fields")
.withAllDeprecated("Set [default_field] to `*` instead"); .withAllDeprecated("Set [default_field] to `*` instead");
private static final ParseField TYPE_FIELD = new ParseField("type"); private static final ParseField TYPE_FIELD = new ParseField("type");

View File

@ -85,7 +85,7 @@ import static org.elasticsearch.common.lucene.search.Queries.newUnmappedFieldQue
/** /**
* A {@link XQueryParser} that uses the {@link MapperService} in order to build smarter * A {@link XQueryParser} that uses the {@link MapperService} in order to build smarter
* queries based on the mapping information. * queries based on the mapping information.
* This class uses {@link MultiMatchQuery} to build the text query around logical operators and {@link XQueryParser} * This class uses {@link MultiMatchQuery} to build the text query around operators and {@link XQueryParser}
* to assemble the result logically. * to assemble the result logically.
*/ */
public class QueryStringQueryParser extends XQueryParser { public class QueryStringQueryParser extends XQueryParser {

View File

@ -58,7 +58,7 @@
* The `split_on_whitespace` parameter for the `query_string` query has been removed. * The `split_on_whitespace` parameter for the `query_string` query has been removed.
If provided, it will be ignored and issue a deprecation warning. If provided, it will be ignored and issue a deprecation warning.
The `query_string` query now splits on logical operator only. The `query_string` query now splits on operator only.
* The `use_dismax` parameter for the `query_string` query has been removed. * The `use_dismax` parameter for the `query_string` query has been removed.
If provided, it will be ignored and issue a deprecation warning. If provided, it will be ignored and issue a deprecation warning.

View File

@ -18,7 +18,7 @@ GET /_search
-------------------------------------------------- --------------------------------------------------
// CONSOLE // CONSOLE
The `query_string` query parses the input and splits text around logical operators. The `query_string` query parses the input and splits text around operators.
Each textual part is analyzed independently of each other. For instance the following query: Each textual part is analyzed independently of each other. For instance the following query:
[source,js] [source,js]
@ -28,14 +28,14 @@ GET /_search
"query": { "query": {
"query_string" : { "query_string" : {
"default_field" : "content", "default_field" : "content",
"query" : "(new york) AND ny" "query" : "field:new york AND city"
} }
} }
} }
-------------------------------------------------- --------------------------------------------------
// CONSOLE // CONSOLE
... will be splitted in `new york` and `ny` and each part is analyzed independently. ... will be splitted in `new`, `york` and `city` and each part is analyzed independently.
When multiple fields are provided it is also possible to modify how the different 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. 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`. The possible modes are described <<multi-match-types, here>> and the default is `best_fields`.