-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Revert 7.x related code from analysis common #118972
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
Conversation
…elastic#113009)" This reverts commit ef37511.
This reverts elastic#113009 and re-adds previous v7 tests since we now support v7 indices as read-only on v9.
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
tokenizers.add(PreConfiguredTokenizer.singleton("pattern", () -> new PatternTokenizer(Regex.compile("\\W+", null), -1))); | ||
tokenizers.add(PreConfiguredTokenizer.singleton("thai", ThaiTokenizer::new)); | ||
// TODO deprecate and remove in API | ||
// This is already broken with normalization, so backwards compat isn't necessary? | ||
tokenizers.add(PreConfiguredTokenizer.singleton("lowercase", XLowerCaseTokenizer::new)); | ||
|
||
// Temporary shim for aliases. TODO deprecate after they are moved |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the TODO still valid here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did some spelunking and believe this was introduced in some darker ages when PRs were still 5 digits long: https://github.com/elastic/elasticsearch/pull/24751/files#diff-dfbfed296c89aa1897a8f3e2ea119717f0c2d2577f4ee9757e5e477d88019f16R309
It somehow survived many code moves. Kudos to that, little friend. I'm pretty sure its time to go now.
This reverts elastic#113009 and re-introduces v7 compatibility logic and previous v7 tests since we now support v7 indices as read-only on v9.
This reverts #113009 and re-introduces v7 compatibility logic and previous v7 tests
since we now support v7 indices as read-only on v9.