Skip to content
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

Merged

Conversation

YeonghyeonKO
Copy link
Contributor

@YeonghyeonKO YeonghyeonKO commented Sep 20, 2024

The method getTokenizers in CommonAnalysisPlugin returns IllegalArgumentException with the message:

The [edgeNGram] tokenizer name was deprecated in 7.6. Please use the tokenizer name to [edge_nGram] for indices created in versions 8 or higher instead.

For IndexVersion 8.x, edge_ngram (not edge_nGram) is the correct name referred as an edgeNGram 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.

Copy link

cla-checker-service bot commented Sep 20, 2024

💚 CLA has been signed

@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label external-contributor Pull request authored by a developer outside the Elasticsearch team v8.16.0 labels Sep 20, 2024
@YeonghyeonKO YeonghyeonKO force-pushed the fix/analysis-tokenizer-edgeNGram branch from e1b8f24 to 36c2cf1 Compare September 20, 2024 11:26
@YeonghyeonKO YeonghyeonKO changed the title Fix exception message when validating the name of tokenizer(edgeNGram) [8.x] Fix exception message when validating the name of tokenizer(edgeNGram) Sep 20, 2024
@YeonghyeonKO
Copy link
Contributor Author

@carlosdelest
As an external contributor in Elasticsearch, I have no authority to assign you as an assginee/reviewer.

@carlosdelest carlosdelest self-assigned this Sep 23, 2024
@carlosdelest carlosdelest added >non-issue Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch :Search Relevance/Search Catch all for Search Relevance labels Sep 23, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-search-relevance (Team:Search Relevance)

@elasticsearchmachine elasticsearchmachine removed the needs:triage Requires assignment of a team area label label Sep 23, 2024
@carlosdelest
Copy link
Member

@elasticsearchmachine test this please

@carlosdelest
Copy link
Member

@elasticmachine run elasticsearch-ci/packaging-tests-windows-sample

@carlosdelest
Copy link
Member

@elasticsearchmachine update branch

@carlosdelest
Copy link
Member

@elasticmachine update branch

@carlosdelest
Copy link
Member

@elasticsearchmachine test this please

@carlosdelest
Copy link
Member

@elasticmachine run elasticsearch-ci/part-1

@carlosdelest
Copy link
Member

@elasticmachine test this please

@carlosdelest
Copy link
Member

@elasticmachine update branch

@carlosdelest
Copy link
Member

@elasticmachine test this please

@carlosdelest carlosdelest merged commit cbce0a6 into elastic:8.x Sep 26, 2024
16 checks passed
@carlosdelest
Copy link
Member

It took a while to pass CI on this. Thanks for contributing to Elastic @YeonghyeonKO !

@YeonghyeonKO
Copy link
Contributor Author

@carlosdelest Thank you for reviewing my PR. It took quite long to pass elasticsearch-ci indeed haha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external-contributor Pull request authored by a developer outside the Elasticsearch team >non-issue :Search Relevance/Search Catch all for Search Relevance Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch v8.16.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants