Preconfigured word_delimiter_graph token filter has incorrect adjust_offsets default
#43621
Assignees
Labels
>bug
:Search Relevance/Analysis
How text is split into tokens
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
Comments
|
Pinging @elastic/es-search |
romseygeek
added a commit
to romseygeek/elasticsearch
that referenced
this issue
Jun 26, 2019
romseygeek
added a commit
that referenced
this issue
Jun 27, 2019
When a named token filter or char filter is passed as part of an Analyze API request with no index, we currently try and build the relevant filter using no index settings. However, this can miss cases where there is a pre-configured filter defined in the analysis registry. One example here is the elision filter, which has a pre-configured version built with the french elision set; when used as part of normal analysis, this preconfigured set is used, but when used as part of the Analyze API we end up with NPEs because it tries to instantiate the filter with no index settings. This commit changes the Analyze API to check for pre-configured filters in the case that the request has no index defined, and is using a name rather than a custom definition for a filter. It also changes the pre-configured `word_delimiter_graph` filter and `edge_ngram` tokenizer to make their settings consistent with the defaults used when creating them with no settings Closes #43002 Closes #43621 Closes #43582
javanna
added
the
Team:Search Relevance
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The standard factory and docs both have
adjust_offsetsasfalse, but the preconfigured filter has it set totrue.The text was updated successfully, but these errors were encountered: