You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to avoid having this (two "bananas"):
["apple", "banana", "carrot", "pineapple", "banana"]
But what about spelling errors?
["apple", "banana", "carrot", "pineapple", "bananna"]
Or plurals?
["apple", "banana", "carrot", "pineapple", "bananas"]
Or punctuation?
["apple", "green apple", "green_apple", "green-apple"]
This brings up a few questions:
Should we even allow dashes and underscores, or should it only be alphanumeric characters and spaces?
Where do we draw the line on fuzzy matching thresholds to cater for spelling errors/variances?
Do we keep it simple and only filter exact matches?
If we decide to allow exact duplicates, how does this affect Elasticsearch's ranking (e.g., does ["apple", "apple", "banana"] come up before ["apple", "banana"] when searching for "apple"?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The idea is to avoid having this (two "bananas"):
["apple", "banana", "carrot", "pineapple", "banana"]
But what about spelling errors?
["apple", "banana", "carrot", "pineapple", "bananna"]
Or plurals?
["apple", "banana", "carrot", "pineapple", "bananas"]
Or punctuation?
["apple", "green apple", "green_apple", "green-apple"]
This brings up a few questions:
Beta Was this translation helpful? Give feedback.
All reactions