Repository navigation
feature/7786-improve-search-precision - #287
Merged
Merged
Conversation
This branch was previously deployed
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
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.
Change
links.titleandsummaries.creditsfree-text clauses frommatchtomatch_phrase.These fields previously used
match, which defaults to OR operator. For long search text such as:imos - satellite remote sensing - sst - l3s - multi sensor - 1 month - night time - australiaa record could score if
links.titleorsummaries.creditscontained any individual term. This produced many irrelevant results, including more than 5000 matches in the example above.With
match_phrase, these fields now only contribute when the terms appear as the same phrase, in order. This makes long-title searches more precise while leaving the other search fields unchanged.