[[configuring-analyzers]] === Configuring built-in analyzers The built-in analyzers can be used directly without any configuration. Some of them, however, support configuration options to alter their behaviour. For instance, the <> can be configured to support a list of stop words: [source,js] -------------------------------- PUT my_index { "settings": { "analysis": { "analyzer": { "std_english": { <1> "type": "standard", "stopwords": "_english_" } } } }, "mappings": { "my_type": { "properties": { "my_text": { "type": "text", "analyzer": "standard", <2> "fields": { "english": { "type": "text", "analyzer": "std_english" <3> } } } } } } } GET _cluster/health?wait_for_status=yellow POST my_index/_analyze { "field": "my_text", <2> "text": "The old brown cow" } POST my_index/_analyze { "field": "my_text.english", <3> "text": "The old brown cow" } -------------------------------- // CONSOLE <1> We define the `std_english` analyzer to be based on the `standard` analyzer, but configured to remove the pre-defined list of English stopwords. <2> The `my_text` field uses the `standard` analyzer directly, without any configuration. No stop words will be removed from this field. The resulting terms are: `[ the, old, brown, cow ]` <3> The `my_text.english` field uses the `std_english` analyzer, so English stop words will be removed. The resulting terms are: `[ old, brown, cow ]` ///////////////////// [source,js] ---------------------------- { "tokens": [ { "token": "old", "start_offset": 4, "end_offset": 7, "type": "", "position": 1 }, { "token": "brown", "start_offset": 8, "end_offset": 13, "type": "", "position": 2 }, { "token": "cow", "start_offset": 14, "end_offset": 17, "type": "", "position": 3 } ] } ---------------------------- // TESTRESPONSE /////////////////////