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.

Sign up for GitHub

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

Jump to bottom

update EdgeNGramTokenizer.DEFAULT_MAX_NGRAM_SIZE to be practical #13813

Closed
wants to merge 2 commits into from
Closed

update EdgeNGramTokenizer.DEFAULT_MAX_NGRAM_SIZE to be practical #13813

wants to merge 2 commits into from

Conversation

YeonghyeonKO
Copy link

issue : #13802

  • Many libraries(git code: Elasticsearch, OpenSearch) based on Lucene use NGramTokenizer.DEFAULT_MAX_NGRAM_SIZE instead of EdgeNGramTokenizer's when configuring an EdgeNGramTokenizer.
  • By the above reason, it's NOT practical to keep sticking DEFAULT_MAX_NGRAM_SIZE of EdgeNGramTokenizer to be ONE.

@YeonghyeonKO
update EdgeNGramTokenizer.DEFAULT_MAX_NGRAM_SIZE to be practical
df7f019 
- Many libraries(git code: Elasticsearch, OpenSearch) use NGramTokenizer.DEFAULT_MAX_NGRAM_SIZE instead of EdgeNGramTokenizer's. 
- By the above reason, it's NOT practical to keep sticking DEFAULT_MAX_NGRAM_SIZE of EdgeNGramTokenizer to be ONE.
@YeonghyeonKO YeonghyeonKO marked this pull request as draft September 20, 2024 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@YeonghyeonKO