Skip to content

Commit

Permalink
Language analyzers small refactor (#8479)
Browse files Browse the repository at this point in the history
Signed-off-by: kolchfa-aws <[email protected]>
  • Loading branch information
kolchfa-aws authored Oct 8, 2024
1 parent c4d94fe commit 3f77141
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions _analyzers/language-analyzers.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ redirect_from:
- /query-dsl/analyzers/language-analyzers/
---

# Language analyzer
# Language analyzers

OpenSearch supports the following language values with the `analyzer` option:
OpenSearch supports the following language analyzers:
`arabic`, `armenian`, `basque`, `bengali`, `brazilian`, `bulgarian`, `catalan`, `czech`, `danish`, `dutch`, `english`, `estonian`, `finnish`, `french`, `galician`, `german`, `greek`, `hindi`, `hungarian`, `indonesian`, `irish`, `italian`, `latvian`, `lithuanian`, `norwegian`, `persian`, `portuguese`, `romanian`, `russian`, `sorani`, `spanish`, `swedish`, `turkish`, and `thai`.

To use the analyzer when you map an index, specify the value within your query. For example, to map your index with the French language analyzer, specify the `french` value for the analyzer field:
Expand Down Expand Up @@ -41,4 +41,4 @@ PUT my-index
}
```

<!-- TO do: each of the options needs its own section with an example. Convert table to individual sections, and then give a streamlined list with valid values. -->
<!-- TO do: each of the options needs its own section with an example. Convert table to individual sections, and then give a streamlined list with valid values. -->

0 comments on commit 3f77141

Please sign in to comment.