-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[8.x] Fix exception message when validating the name of tokenizer(edgeNGram) #113257
[8.x] Fix exception message when validating the name of tokenizer(edgeNGram) #113257
Conversation
💚 CLA has been signed |
e1b8f24
to
36c2cf1
Compare
@carlosdelest |
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
@elasticsearchmachine test this please |
@elasticmachine run elasticsearch-ci/packaging-tests-windows-sample |
@elasticsearchmachine update branch |
@elasticmachine update branch |
@elasticsearchmachine test this please |
@elasticmachine run elasticsearch-ci/part-1 |
@elasticmachine test this please |
@elasticmachine update branch |
@elasticmachine test this please |
It took a while to pass CI on this. Thanks for contributing to Elastic @YeonghyeonKO ! |
@carlosdelest Thank you for reviewing my PR. It took quite long to pass elasticsearch-ci indeed haha |
The method
getTokenizers
inCommonAnalysisPlugin
returns IllegalArgumentException with the message:For IndexVersion 8.x,
edge_ngram
(notedge_nGram
) is the correct name referred as anedgeNGram
tokenizer so I ask to change the word in this Pull Request. The PR could reduce confusion in defining edgeNGram tokenizers when statically mapping indices in Elasticsearch 8.x.After 9.x version, @javanna's PR had made the deprecation issue clear and already been merged into
main
branch, so there is no problem.