mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-03-02 08:59:09 +00:00
7ef906fde8
Adds a 'Configure text analysis' page to house tutorial content for the analysis topic. Also relocates the following pages as children as this new page: * 'Test an analyzer' * 'Configuring built-in analyzers' * 'Create a custom analyzer' I plan to add a tutorial for specifying index-time and search-time analyzers to this section as part of a future PR.
29 lines
1.1 KiB
Plaintext
29 lines
1.1 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>>
|
|
|
|
|
|
include::testing.asciidoc[]
|
|
|
|
include::analyzers/configuring.asciidoc[]
|
|
|
|
include::analyzers/custom-analyzer.asciidoc[] |