Specifying a custom analyzer on an index allows you to set custom tokenizers and token filters.
In #2278787-2: Wildcard? → , there was interest in using the edge n-gram tokenizer to allow searching with a wildcard.
Note that the edge n-gram tokenzier works particularly well when used to tokenize fields that are used for Elasticsearch's search-as-you-type functionality (which is exposed with Elasticsearch Connector's integration with Search API Autocomplete → ).
Make it possible to define custom analyzers for an index.
To be determined.
To be determined.
To be determined.
This issue has been discussed here but as it is not exactly connected with the wildcards we have moved it as a separate one: #2278787-2: Wildcard? →
Active
8.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
It is still possible to create a custom analyzer for an index in the latest versions of Elasticsearch, and I think this would be a desirable feature for the 8.0.x version too. So I'm moving this into the 8.0.x queue.
Note that the nGram and edgeNGram token filter names and similar tokenizer names were deprecated in versions 6.4 and 7.6 respectively; and were removed in Elasticsearch 8.0 — the new names are ngram and edge_ngram in both cases.