Beidermorse encoder does not support "replace" option

Beidermorse encoder does not support "replace" option: only new tokens will be returned.
One of the backfires is that highlighting will not work.
This is actually because Lucene's beidermorse filter does not support this option.
Please consider to update documentation by specifying which encore support `"replace : false"` option.

Closes #22.

(cherry picked from commit c307877)
This commit is contained in:
David Pilato 2014-05-28 13:04:16 +02:00
parent 868fd81d73
commit 39feb530d8
1 changed files with 20 additions and 15 deletions

View File

@ -28,25 +28,30 @@ A `phonetic` token filter that can be configured with different `encoder` types:
The `replace` parameter (defaults to `true`) controls if the token processed The `replace` parameter (defaults to `true`) controls if the token processed
should be replaced with the encoded one (set it to `true`), or added (set it to `false`). should be replaced with the encoded one (set it to `true`), or added (set it to `false`).
{ ```js
"index" : { {
"analysis" : { "index" : {
"analyzer" : { "analysis" : {
"my_analyzer" : { "analyzer" : {
"tokenizer" : "standard", "my_analyzer" : {
"filter" : ["standard", "lowercase", "my_metaphone"] "tokenizer" : "standard",
} "filter" : ["standard", "lowercase", "my_metaphone"]
}, }
"filter" : { },
"my_metaphone" : { "filter" : {
"type" : "phonetic", "my_metaphone" : {
"encoder" : "metaphone", "type" : "phonetic",
"replace" : false "encoder" : "metaphone",
} "replace" : false
} }
} }
} }
} }
}
```
Note that `beidermorse` does not support `replace` parameter.
Questions Questions
--------- ---------