ngram "suggest" field for users, tracks, playlists #187
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.
Users, tracks, playlists all get a
suggestfield which is analyzed with 2gram + 3gram analyzer. So searchinginfixwill findsome_infix_handle.Also uses a minimum should match of 80% on the ngram field AND enables fuzzy AUTO... so we have fuzzy ngrams. So searching
monoistwill surfacemonistThis increases recall a fair bit, so almost all queries will likely have results.
If results are verging on "irrelevant" (i.e. precision of top 10 results is bad) there are a few options:
minimum_should_matchto90%title^20shouldquery terms with higher boost