[Docs] Add note about maximum token length for whitespace tokenizer #26721
Conversation
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
cbuescher
added
:Search Relevance/Analysis
cbuescher
changed the title
cbuescher
force-pushed
the
docs-addNote-WhitespaceTokenizer
branch
from
4a2d047 to
5d1627c
Compare
Member
Author
|
This clarifies the docs in 5.6.x and 6.0 while starting with 6.1 we will have support for an overwrite of the "max_token_length" parameter via #26643. |
jpountz
approved these changes
Oct 6, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
The whitespace tokenizer splits tokens longer than 255 characters into multiple tokens,
which can lead to confusing search matches like the one observed in #26601. This adds
a note to the documentation to make this clearer.
Closes #26641