Fix typo in analysis doc. #31797
Closed
Fix typo in analysis doc. #31797
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
The source text "lazy" would be converted into "lazy" within the inverted index, not "lazi".
Member
|
@lcawl it would probably make sense to add a short note why this example is the way it is, wdyt? |
Contributor
|
I agree, it looked like a typo. Adding @Sue-Gallagher |
Author
|
It's true, "lazy" comes back as "lazi" from the english analyser! Thanks for pointing this out @cbuescher |
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this pull request
Jul 6, 2018
There have been at least two PRs trying to fix the spelling of "lazi" because it isn't very clear from the example that the english analyzer will stem each token in the example. This adds a short description of the analysis process to make this clearer. Relates to elastic#31797
cbuescher
pushed a commit
that referenced
this pull request
Jul 6, 2018
There have been at least two PRs trying to fix the spelling of "lazi" because it isn't very clear from the example that the english analyzer will stem each token in the example. This adds a short description of the analysis process to make this clearer. Relates to #31797
cbuescher
pushed a commit
that referenced
this pull request
Jul 6, 2018
There have been at least two PRs trying to fix the spelling of "lazi" because it isn't very clear from the example that the english analyzer will stem each token in the example. This adds a short description of the analysis process to make this clearer. Relates to #31797
cbuescher
pushed a commit
that referenced
this pull request
Jul 6, 2018
There have been at least two PRs trying to fix the spelling of "lazi" because it isn't very clear from the example that the english analyzer will stem each token in the example. This adds a short description of the analysis process to make this clearer. Relates to #31797
cbuescher
pushed a commit
that referenced
this pull request
Jul 6, 2018
There have been at least two PRs trying to fix the spelling of "lazi" because it isn't very clear from the example that the english analyzer will stem each token in the example. This adds a short description of the analysis process to make this clearer. Relates to #31797
cbuescher
pushed a commit
that referenced
this pull request
Jul 6, 2018
There have been at least two PRs trying to fix the spelling of "lazi" because it isn't very clear from the example that the english analyzer will stem each token in the example. This adds a short description of the analysis process to make this clearer. Relates to #31797
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 source text "lazy" would be converted into "lazy" within the inverted index, not "lazi".