Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MB-61640: Fuzzy Dynamic Scoring #2056

Merged
merged 2 commits into from
Nov 21, 2024
Merged

MB-61640: Fuzzy Dynamic Scoring #2056

merged 2 commits into from
Nov 21, 2024

Conversation

Likith101
Copy link
Member

@Likith101 Likith101 commented Jul 24, 2024

  • Added levenshtein distance calculation for fuzzy and wildcard searchers
  • Added new implementations of certain functions to allow passing of edit distances per term
  • Multiplied boosts by inverse of edit distance for score calculation

search/searcher/search_fuzzy.go Outdated Show resolved Hide resolved
search/searcher/search_fuzzy.go Outdated Show resolved Hide resolved
search/searcher/search_multi_term.go Show resolved Hide resolved
@CascadingRadium
Copy link
Member

also please add unit tests to show the effect (with and w/o boost) across match and match_phrase queries thanks

@abhinavdangeti abhinavdangeti modified the milestone: v2.4.3 Aug 6, 2024
@abhinavdangeti abhinavdangeti added this to the v2.5.0 milestone Sep 18, 2024
@Likith101 Likith101 changed the title MB-61640: Toy: Fuzzy and Wildcard dynamic scoring MB-61640: Fuzzy Dynamic Scoring Oct 22, 2024
Likith101 and others added 2 commits November 20, 2024 10:10
 - Added new implementations of certain functions to allow passing of edit distances per term
 - Propagated edit distances from vellum
 - Boosting each term based on the inverse of its fuzziness
@Likith101 Likith101 merged commit 38f1737 into master Nov 21, 2024
9 checks passed
@abhinavdangeti abhinavdangeti deleted the fuzzyScoring branch November 22, 2024 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants