-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
search_analyzer definitions in index settings to allow for dynamic updates to query-time analyzers #28877
Comments
search_analyzer
definitions in index settings
search_analyzer
definitions in index settings
The |
/cc @elastic/es-search-aggs |
@osman being able to update search analyzers (specifically being able to update the synonyms in a synonym token filter only used at search time) is something we are actively thinking about. However it is not so straight-forward since a token filter can be used by any analyzer and any analyzer can be used as either an "analyzer" or "search_analyzer" in the mappings. This means that determining if a synonym list can be updated would currently require going through all the analysis settings and mappings which is not a great solution. We have spoken about denoting token filter definitions as "search only" but there is more thinking to be done around how this actually plays out when validating analyzer settings and mappings and when trying to update the synonym list |
Pinging @elastic/es-search (Team:Search) |
Closing this issue as implemented. Synonym filters can be updateable with property: "updateable": true and file based synonyms can be reloaded. Alternatively Synonyms Management API can be used to manage synonyms in an internal system index. |
something like this:
This denotes the analyzer as one that is only used at search time, and is thus safe to update dynamically. My use-case is dynamically updating synonyms without having the open/close the index. But I imagine there are other useful properties to being able to dynamically update analyzers used only at query time.
The text was updated successfully, but these errors were encountered: