Adding standard analyzer docs #8528
Conversation
Signed-off-by: Anton Rubin <[email protected]>
AntonEliatra
requested review from
kolchfa-aws,
Naarcha-AWS,
vagimeli,
AMoo-Miki,
natebower,
dlvenable and
epugh
as code owners
|
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
Signed-off-by: Anton Rubin <[email protected]>
Signed-off-by: Anton Rubin <[email protected]>
|
@udabhas @varun-lodaya Please provide tech review approval to move this PR forward in the documentation process. Please review this week or provide a peer who can review it. Thank you. |
vagimeli
added
3 - Tech review
Signed-off-by: Fanit Kolchina <[email protected]>
kolchfa-aws
added
5 - Editorial review
|
|
||
| This analyzer consists of the following tokenizers and token filters: | ||
|
|
||
| - `standard` tokenizer: Removes most punctuation and splits text on spaces and other common delimiters. |
There was a problem hiding this comment.
| - `standard` tokenizer: Removes most punctuation and splits text on spaces and other common delimiters. | |
| - `standard` tokenizer: Removes most punctuation and splits text at spaces and other common delimiters. |
There was a problem hiding this comment.
Will consistently use "on".
| The `standard` analyzer is the default analyzer that is used when no other analyzer is specified. It is designed to provide a basic and efficient approach for generic text processing. | ||
|
|
||
| This analyzer consists of the following tokenizers and token filters: | ||
|
|
There was a problem hiding this comment.
Line 13: I believe we had been using "split text at" (as opposed to "on"), but "on" started appearing in recent docs. Please ensure global consistency.
There was a problem hiding this comment.
Will address this as a separate PR globally.
Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: kolchfa-aws <[email protected]>
* adding standard analyzer docs Signed-off-by: Anton Rubin <[email protected]> * adding further details Signed-off-by: Anton Rubin <[email protected]> * adding more examples Signed-off-by: Anton Rubin <[email protected]> * Doc review Signed-off-by: Fanit Kolchina <[email protected]> * Apply suggestions from code review Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> --------- Signed-off-by: Anton Rubin <[email protected]> Signed-off-by: Fanit Kolchina <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> Co-authored-by: Fanit Kolchina <[email protected]> Co-authored-by: kolchfa-aws <[email protected]> Co-authored-by: Nathan Bower <[email protected]> (cherry picked from commit b81500f) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
Adding standard analyzer docs
Issues Resolved
Part of #1483 addressed in this PR.
Version
all
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.