The synonym rules should not contain words that are removed by a filter that appears later in the chain (like a stop filter).
This means that all the synonyms defined there needs to be in lowercase, or they won’t be found by the synonyms filter.
In the above example, text will be lowercased by the lowercase filter before being processed by the synonyms_filter. Text will be processed first through filters preceding the synonym filter before being processed by the synonym filter. Order is important for your token filters. To apply synonyms, you will need to include a synonym token filters into an analyzer: Configure analyzers with synonym token filters edit The ignore_case parameter works with tokenizer parameter only. Tokenize the synonym, this parameter is for backwards compatibility for indices that created before 6.0. The tokenizer parameter controls the tokenizers that will be used to tokenizer and ignore_case are deprecated edit However, ifĮxpand=true then the mappings added would be equivalent to foo, baz => foo, baz i.e, all mappings other than the Set to false no mapping would get added as when expand=false the target mapping is the first word. Similarly, if the mapping was "bar, foo, baz" and expand was Mapping is itself eliminated because it was a stop word. However, if the mappingīeing added was foo, baz => bar nothing would get added to the synonym list. With the above request the word bar gets skipped but a mapping foo => baz is still added.
0 kommentar(er)
