honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Docs: Fixed a bad ref on lang analyzers page

This commit is contained in:
Clinton Gormley 2014-06-09 23:03:12 +02:00
parent 5c5c1da06c
commit 5e40868f44
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/reference/analysis/analyzers/lang-analyzer.asciidoc
View File

@ -782,7 +782,7 @@ The `greek` analyzer could be reimplemented as a `custom` analyzer as follows:
The `hindi` analyzer cannot currently be implemented as a `custom` analyzer The `hindi` analyzer cannot currently be implemented as a `custom` analyzer
as it depends on the IndicNormalizationFilter and HindiNormalizationFilter as it depends on the IndicNormalizationFilter and HindiNormalizationFilter
which are not yet exposed by Elasticsearch. Instead, see the <<icu-analysis-plugin>>. which are not yet exposed by Elasticsearch. Instead, see the <<analysis-icu-plugin>>.
[[hungarian-analyzer]] [[hungarian-analyzer]]
==== `hungarian` analyzer ==== `hungarian` analyzer
@ -1239,12 +1239,12 @@ The `swedish` analyzer could be reimplemented as a `custom` analyzer as follows:
The `turkish` analyzer cannot currently be implemented as a `custom` analyzer The `turkish` analyzer cannot currently be implemented as a `custom` analyzer
because it depends on the TurkishLowerCaseFilter and the ApostropheFilter because it depends on the TurkishLowerCaseFilter and the ApostropheFilter
which are not exposed in Elasticsearch. Instead, see the <<icu-analysis-plugin>>. which are not exposed in Elasticsearch. Instead, see the <<analysis-icu-plugin>>.
[[thai-analyzer]] [[thai-analyzer]]
==== `thai` analyzer ==== `thai` analyzer
The `thai` analyzer cannot currently be implemented as a `custom` analyzer The `thai` analyzer cannot currently be implemented as a `custom` analyzer
because it depends on the ThaiTokenizer which is not exposed in Elasticsearch. because it depends on the ThaiTokenizer which is not exposed in Elasticsearch.
Instead, see the <<icu-analysis-plugin>>. Instead, see the <<analysis-icu-plugin>>.