Clarifies how the query_string splits textual part to build a query#28798
Merged
jimczi merged 2 commits intoelastic:masterfrom Mar 1, 2018
Merged
Clarifies how the query_string splits textual part to build a query#28798jimczi merged 2 commits intoelastic:masterfrom
jimczi merged 2 commits intoelastic:masterfrom
Conversation
Whitespaces are not considered as operators anymore in 6x but the documentation is not clear about it. This commit changes the example in the documentation and adds a note regarding whitespaces and operators. Closes elastic#28719
dakrone
approved these changes
Feb 23, 2018
Member
dakrone
left a comment
There was a problem hiding this comment.
I left grammatical comments, but no need for another review once they're addressed
| // CONSOLE | ||
|
|
||
| ... will be splitted in `new`, `york` and `city` and each part is analyzed independently. | ||
| ... will be splitted in `new york city` and `big apple` and each part is then |
Member
There was a problem hiding this comment.
"will be spitted in" -> "will be split into"
| ... will be splitted in `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 as operators, this means that `new york city` |
| analyzed independently by the analyzer configured for the field. | ||
|
|
||
| WARNING: Whitespaces are not considered as operators, this means that `new york city` | ||
| will be pass "as is" to the analyzer configured for the field. If the field is a `keyword` |
jimczi
added a commit
that referenced
this pull request
Mar 1, 2018
* Clarifies how the query_string splits textual part to build a query Whitespaces are not considered as operators anymore in 6x but the documentation is not clear about it. This commit changes the example in the documentation and adds a note regarding whitespaces and operators. Closes #28719
jimczi
added a commit
that referenced
this pull request
Mar 1, 2018
* Clarifies how the query_string splits textual part to build a query Whitespaces are not considered as operators anymore in 6x but the documentation is not clear about it. This commit changes the example in the documentation and adds a note regarding whitespaces and operators. Closes #28719
jimczi
added a commit
that referenced
this pull request
Mar 1, 2018
* Clarifies how the query_string splits textual part to build a query Whitespaces are not considered as operators anymore in 6x but the documentation is not clear about it. This commit changes the example in the documentation and adds a note regarding whitespaces and operators. Closes #28719
jimczi
added a commit
that referenced
this pull request
Mar 1, 2018
* Clarifies how the query_string splits textual part to build a query Whitespaces are not considered as operators anymore in 6x but the documentation is not clear about it. This commit changes the example in the documentation and adds a note regarding whitespaces and operators. Closes #28719
martijnvg
added a commit
that referenced
this pull request
Mar 8, 2018
* es/master: (48 commits) Update bucket-sort-aggregation.asciidoc (#28937) [Docs] REST high-level client: Fix code for most basic search request (#28916) Improved percolator's random candidate query duel test and fixed bugs that were exposed by this: Revert "Rescore collapsed documents (#28521)" Build: Fix test logger NPE when no tests are run (#28929) [TEST] AwaitsFix QueryRescorerIT.testRescoreAfterCollapse Decouple XContentType from StreamInput/Output (#28927) Remove BytesRef usage from XContentParser and its subclasses (#28792) [DOCS] Correct typo in configuration (#28903) Fix incorrect datemath example (#28904) Add a usage example of the JLH score (#28905) Wrap stream passed to createParser in try-with-resources (#28897) Rescore collapsed documents (#28521) Fix (simple)_query_string to ignore removed terms (#28871) [Docs] Fix typo in composite aggregation (#28891) Try if tombstone is eligable for pruning before locking on it's key (#28767) Limit analyzed text for highlighting (improvements) (#28808) Missing `timeout` parameter from the REST API spec JSON files (#28328) Clarifies how query_string splits textual part (#28798) Update outdated java version reference (#28870) ...
martijnvg
added a commit
that referenced
this pull request
Mar 8, 2018
* es/6.x: (48 commits) Update bucket-sort-aggregation.asciidoc (#28937) [Docs] REST high-level client: Fix code for most basic search request (#28916) Improved percolator's random candidate query duel test and fixed bugs that were exposed by this: Revert "Rescore collapsed documents (#28521)" Build: Fix test logger NPE when no tests are run (#28929) [TEST] AwaitsFix QueryRescorerIT.testRescoreAfterCollapse Decouple XContentType from StreamInput/Output (#28927) Remove BytesRef usage from XContentParser and its subclasses (#28792) Add doc note for -server flag on Windows service [DOCS] Correct typo in configuration (#28903) Fix incorrect datemath example (#28904) Add a usage example of the JLH score (#28905) Limit analyzed text for highlighting (improvements) (#28907) Wrap stream passed to createParser in try-with-resources (#28897) [Docs] Fix typo in composite aggregation (#28891) Rescore collapsed documents (#28521) Fix (simple)_query_string to ignore removed terms (#28871) Missing `timeout` parameter from the REST API spec JSON files (#28328) Clarifies how query_string splits textual part (#28798) Update outdated java version reference (#28870) ...
sebasjm
pushed a commit
to sebasjm/elasticsearch
that referenced
this pull request
Mar 10, 2018
* Clarifies how the query_string splits textual part to build a query Whitespaces are not considered as operators anymore in 6x but the documentation is not clear about it. This commit changes the example in the documentation and adds a note regarding whitespaces and operators. Closes elastic#28719
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Whitespaces are not considered as operators anymore in 6x but the documentation is not clear about it.
This commit changes the example in the documentation and adds a note regarding whitespaces and operators.
Closes #28719