PB-1167: improve fuzzy search index configuration #644
Conversation
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
charachters, that's why we have to auomtaically expand keywords on index generation
ltclm
force-pushed
the
fix_PB-1167_fuzzy_search
branch
from
dd9ccf8 to
e362bd1
Compare
ltclm
force-pushed
the
fix_PB-1167_fuzzy_search
branch
3 times, most recently
from
e6b297a to
c352551
Compare
ltclm
force-pushed
the
fix_PB-1167_fuzzy_search
branch
from
c352551 to
d7991cd
Compare
the fuzzy string search Text will be built without wildcards by the wsgi application. we have to enable automated wildcard expansion for infix matches in the index configuration
ltclm
changed the title
faselm
approved these changes
Dec 9, 2024
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.
for fuzzy search requests we will set:
wordforms do not make sense with metaphone morphology. if wordforms are applied on a keyword, the metaphone code won't be build
with the improved fuzzy search in the wsgi app, the keywords will not be prefixed and suffixed with wildcards. we can enable wildcard expansion on all meptahone / fuzzy search indexes