OpenSearch/docs/reference/analysis/configure-text-analysis.asciidoc
James Rodewig 4fcf5a9de4 [DOCS] Rewrite analysis intro (#51184)
* [DOCS] Rewrite analysis intro. Move index/search analysis content.

* Rewrites 'Text analysis' page intro as high-level definition.
  Adds guidance on when users should configure text analysis
* Rewrites and splits index/search analysis content:
  * Conceptual content -> 'Index and search analysis' under 'Concepts'
  * Task-based content -> 'Specify an analyzer' under 'Configure...'
* Adds detailed examples for when to use the same index/search analyzer
  and when not.
* Adds new example snippets for specifying search analyzers

* clarifications

* Add toc. Decrement headings.

* Reword 'When to configure' section

* Remove sentence from tip
2020-01-30 09:32:16 -05:00

32 lines
1.2 KiB
Plaintext

[[configure-text-analysis]]
== Configure text analysis
By default, {es} uses the <<analysis-standard-analyzer,`standard` analyzer>> for
all text analysis. The `standard` analyzer gives you out-of-the-box support for
most natural languages and use cases. If you chose to use the `standard`
analyzer as-is, no further configuration is needed.
If the standard analyzer does not fit your needs, review and test {es}'s other
built-in <<analysis-analyzers,built-in analyzers>>. Built-in analyzers don't
require configuration, but some support options that can be used to adjust their
behavior. For example, you can configure the `standard` analyzer with a list of
custom stop words to remove.
If no built-in analyzer fits your needs, you can test and create a custom
analyzer. Custom analyzers involve selecting and combining different
<<analyzer-anatomy,analyzer components>>, giving you greater control over
the process.
* <<test-analyzer>>
* <<configuring-analyzers>>
* <<analysis-custom-analyzer>>
* <specify-analyer>>
include::testing.asciidoc[]
include::analyzers/configuring.asciidoc[]
include::analyzers/custom-analyzer.asciidoc[]
include::specify-analyzer.asciidoc[]