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
Spellchecker / Fuzzy queries refactoring. #1266
Labels
Projects
Comments
any progress on this? |
At some point, we also used "search" meta-field for term vectors : 13fb6f9 |
romainruaud
added a commit
to romainruaud/elasticsuite
that referenced
this issue
Jan 3, 2023
…g also 'search field'.
romainruaud
added a commit
to romainruaud/elasticsuite
that referenced
this issue
Jan 4, 2023
…g also 'search field'.
romainruaud
added a commit
to romainruaud/elasticsuite
that referenced
this issue
Jan 4, 2023
…g also 'search field'.
romainruaud
added a commit
that referenced
this issue
Jan 11, 2023
Fix #1266 by making the term vectors on all shards and search field.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are functional holes in the spellchecking / fuzzy query building.
termVectors query is run against 'spelling' field, so only against 'is_used_in_spellcheck' fields.
if no results, a fuzzy query is built on 'spelling', and on all 'is_used_in_spellcheck' fields (having a weight > 1).
=> can cause 0 results for a query that should have some (value can exist on a field which is not 'used_in_spellcheck').
The text was updated successfully, but these errors were encountered: