Do not run near queries on qualifier words #3290
Merged
Conversation
This file contains 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
There is too much potential for confusion (e.g. 'Rio Grande' read as 'river near Grande') fir too little gain. Use near phrases instead.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Qualifier words like hotel might sometimes appear in a query where a near search is meant. For example, 'hotels berlin' most like wants to have hotels in Berlin listed. These occasions are rare however ('hotel berlin' is already more likely to be a search for a hotel named Berlin, a true qualifier word). So there is too much potential for confusion (e.g. 'Rio Grande' read as 'river near Grande') for too little gain.
This disables the interpretation of a qualifier word as a near search completely. You can always use a near phrase like 'hotels in berlin' to achieve the same result when searching.
Fixes #3277.