Document nori default XPN stoptag behavior for Korean prefixes#151157
Merged
john-wagster merged 1 commit intoJun 15, 2026
Conversation
Collaborator
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
Contributor
|
@Incheonkirin this looks good to me; thank you much for the docs update. I'll wait a bit in case the docs folks want to comment but otherwise will merge this shortly. |
Member
|
@john-wagster @Incheonkirin docs here - this is ok to merge. this is not the best spot for a big warning, but the page would need to be restructured a bit to make a better spot available - not worth the effort vs. getting this info in. |
Contributor
|
@elasticmachine test this |
Contributor
Author
|
Thanks @john-wagster and @shainaraskas for the quick review and merge — agreed that getting the caveat documented matters more than its placement here. |
valeriy42
pushed a commit
to valeriy42/elasticsearch
that referenced
this pull request
Jun 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a warning to the
nori_part_of_speechtoken filter docs: the defaultstoptagsincludeXPN, so a meaning-carrying Korean prefix emitted asXPNis removed by the defaultnorianalyzer. For example,비급여(non-covered) is analyzed as급여(covered), so the index cannot distinguish the two.The warning shows the
_analyzeoutput and two remedies: registering such terms viauser_dictionary_rules(preserves the full term as a single noun token), or defining a customstoptagslist that omitsXPN(preserves prefix tokens, with possible prefix noise).Closes #151094.