# Specifying Analyzer **URL:** \ **Category:** Elasticsearch\ **Created:** [June 19, 2013, 2:03am UTC](https://discuss.elastic.co/t/specifying-analyzer/12470 "2013-06-19T02:03:49Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Igal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igal/32/1119_2.png) [@Igal](https://discuss.elastic.co/u/Igal)\ **Post date:** [June 19, 2013, 2:03am UTC](https://discuss.elastic.co/t/specifying-analyzer/12470/1 "2013-06-19T02:03:49Z")
I define an analyzer in config/elasticsearch.json like so: { "index": { "analysis": { "analyzer": { "synonym": { "tokenizer": "whitespace", "filter": ["synonym"] } }, "filter": { "synonym": { "type": "synonym", "synonyms\_path": "synonyms.txt" } } } } } I know that this part is processed when ES is starting up because when there is no file at synonyms.txt I see the error in the console and the error goes away when the file is there -- so far so good. it is my understanding that the name of that analyzer is "synonym" (please correct me if I'm wrong). now I'm trying to access that analyzer like so: [http://localhost:9200/\_analyze?text=this+is+a+test&analyzer=synonym](http://localhost:9200/_analyze?text=this+is+a+test&analyzer=synonym) but I get an error 400 - ElasticSearchIllegalArgumentException[failed to find analyzer [synonym]] what am I doing wrong? TIA, Igal -- Igal Sapir Railo Core Developer [http://getRailo.org/](http://getRailo.org/) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [June 19, 2013, 2:39am UTC](https://discuss.elastic.co/t/specifying-analyzer/12470/2 "2013-06-19T02:39:09Z")
You can use a custom analyzer in the Analysis API only after it has been mapped to a field in an index. You don't need to analysis on this field, but the analyzer is not used unless an index that uses it has been created. -- Ivan On Tue, Jun 18, 2013 at 7:03 PM, Igal @ [getRailo.org](http://getRailo.org) [igal@getrailo.org](mailto:igal@getrailo.org)wrote: > I define an analyzer in config/elasticsearch.json like so: > > { > "index": { > "analysis": { > "analyzer": { > "synonym": { > "tokenizer": "whitespace", > "filter": ["synonym"] > } > }, > "filter": { > "synonym": { > "type": "synonym", > "synonyms\_path": "synonyms.txt" > } > } > } > } > } > > I know that this part is processed when ES is starting up because when > there is no file at synonyms.txt I see the error in the console and the > error goes away when the file is there -- so far so good. > > it is my understanding that the name of that analyzer is "synonym" (please > correct me if I'm wrong). > > now I'm trying to access that analyzer like so: > > [http://localhost:9200/\_\*\*analyze?text=this+is+a+test&\*\*analyzer=synonym](http://localhost:9200/_ **analyze?text=this+is+a+test&** analyzer=synonym)[http://localhost:9200/\_analyze?text=this+is+a+test&analyzer=synonym](http://localhost:9200/_analyze?text=this+is+a+test&analyzer=synonym) > > but I get an error 400 - ElasticSearchIllegalArgumentEx\*\*ception[failed > to find analyzer [synonym]] > > what am I doing wrong? > > TIA, > > Igal > > -- > Igal Sapir > Railo Core Developer > [http://getRailo.org/](http://getRailo.org/) > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscribe@\*\*[googlegroups.com](http://googlegroups.com)[elasticsearch%2Bunsubscribe@googlegroups.com](mailto:elasticsearch%2Bunsubscribe@googlegroups.com) > . > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > . -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Igal\_2](https://avatars.discourse-cdn.com/v4/letter/i/e0b2c6/32.png) [@Igal\_2](https://discuss.elastic.co/u/Igal_2)\ **Post date:** [June 19, 2013, 3:14am UTC](https://discuss.elastic.co/t/specifying-analyzer/12470/3 "2013-06-19T03:14:59Z")
thanks Ivan, so how would I map it to a field? I tried: PUT /testindex/\_mapping { "mappings" : { "type1" : { "properties" : { "field1" : { "type" : "string", "analyzer" : "synonym" } } } } } but I get an error 500 -- ElasticSearchIllegalArgumentException: failed to find analyzer [synonym] On Tuesday, June 18, 2013 7:39:09 PM UTC-7, Ivan Brusic wrote: > You can use a custom analyzer in the Analysis API only after it has been > mapped to a field in an index. You don't need to analysis on this field, > but the analyzer is not used unless an index that uses it has been created. > > -- > Ivan > > On Tue, Jun 18, 2013 at 7:03 PM, Igal @ [getRailo.org](http://getRailo.org) \<[ig...@getrailo.org](mailto:ig...@getrailo.org)\ > > > wrote: > > > I define an analyzer in config/elasticsearch.json like so: > > > > { > > "index": { > > "analysis": { > > "analyzer": { > > "synonym": { > > "tokenizer": "whitespace", > > "filter": ["synonym"] > > } > > }, > > "filter": { > > "synonym": { > > "type": "synonym", > > "synonyms\_path": "synonyms.txt" > > } > > } > > } > > } > > } > > > > I know that this part is processed when ES is starting up because when > > there is no file at synonyms.txt I see the error in the console and the > > error goes away when the file is there -- so far so good. > > > > it is my understanding that the name of that analyzer is "synonym" > > (please correct me if I'm wrong). > > > > now I'm trying to access that analyzer like so: > > > > [http://localhost:9200/\_\*\*analyze?text=this+is+a+test&\*\*analyzer=synonym](http://localhost:9200/_ **analyze?text=this+is+a+test&** analyzer=synonym)[http://localhost:9200/\_analyze?text=this+is+a+test&analyzer=synonym](http://localhost:9200/_analyze?text=this+is+a+test&analyzer=synonym) > > > > but I get an error 400 - ElasticSearchIllegalArgumentEx\*\*ception[failed > > to find analyzer [synonym]] > > > > what am I doing wrong? > > > > TIA, > > > > Igal > > > > -- > > Igal Sapir > > Railo Core Developer > > [http://getRailo.org/](http://getRailo.org/) > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com) \. > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > > . -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [June 19, 2013, 3:18am UTC](https://discuss.elastic.co/t/specifying-analyzer/12470/4 "2013-06-19T03:18:13Z")
Have you tried using the index in the analysis call? [http://localhost:9200/\*testindex\*/\_\*\*analyze?text=this+is+a+test&](http://localhost:9200/*testindex*/_**analyze?text=this+is+a+test&)\*\* analyzer=synonym[http://localhost:9200/\_analyze?text=this+is+a+test&analyzer=synonym](http://localhost:9200/_analyze?text=this+is+a+test&analyzer=synonym) On Tue, Jun 18, 2013 at 8:14 PM, Igal [dev@21solutions.net](mailto:dev@21solutions.net) wrote: > thanks Ivan, > > so how would I map it to a field? > > I tried: > > PUT /testindex/\_mapping > { > "mappings" : { > "type1" : { > "properties" : { > "field1" : { "type" : "string", "analyzer" : "synonym" } > } > } > } > } > > but I get an error 500 -- ElasticSearchIllegalArgumentException: failed to > find analyzer [synonym] > > On Tuesday, June 18, 2013 7:39:09 PM UTC-7, Ivan Brusic wrote: > > > You can use a custom analyzer in the Analysis API only after it has been > > mapped to a field in an index. You don't need to analysis on this field, > > but the analyzer is not used unless an index that uses it has been created. > > > > -- > > Ivan > > > > On Tue, Jun 18, 2013 at 7:03 PM, Igal @ [getRailo.org](http://getRailo.org) [ig...@getrailo.org](mailto:ig...@getrailo.org)wrote: > > > > > I define an analyzer in config/elasticsearch.json like so: > > > > > > { > > > "index": { > > > "analysis": { > > > "analyzer": { > > > "synonym": { > > > "tokenizer": "whitespace", > > > "filter": ["synonym"] > > > } > > > }, > > > "filter": { > > > "synonym": { > > > "type": "synonym", > > > "synonyms\_path": "synonyms.txt" > > > } > > > } > > > } > > > } > > > } > > > > > > I know that this part is processed when ES is starting up because when > > > there is no file at synonyms.txt I see the error in the console and the > > > error goes away when the file is there -- so far so good. > > > > > > it is my understanding that the name of that analyzer is "synonym" > > > (please correct me if I'm wrong). > > > > > > now I'm trying to access that analyzer like so: > > > > > > [http://localhost:9200/\_\*\*analyze\*\*?text=this+is+a+test&\*\*analyzer=](http://localhost:9200/_ **analyze**?text=this+is+a+test&**analyzer=)\*\* > > > synonym[http://localhost:9200/\_analyze?text=this+is+a+test&analyzer=synonym](http://localhost:9200/_analyze?text=this+is+a+test&analyzer=synonym) > > > > > > but I get an error 400 - ElasticSearchIllegalArgumentEx\*\*\*\*ception[failed > > > to find analyzer [synonym]] > > > > > > what am I doing wrong? > > > > > > TIA, > > > > > > Igal > > > > > > -- > > > Igal Sapir > > > Railo Core Developer > > > [http://getRailo.org/](http://getRailo.org/) > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to elasticsearc...@ **goog** [legroups.com](http://legroups.com). > > > > > > For more options, visit [https://groups.google.com/\*\*grou\*\*ps/opt\_out](https://groups.google.com/ **grou** ps/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > > > . > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Igal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igal/32/1119_2.png) [@Igal](https://discuss.elastic.co/u/Igal)\ **Post date:** [June 19, 2013, 3:45am UTC](https://discuss.elastic.co/t/specifying-analyzer/12470/5 "2013-06-19T03:45:42Z")
I tried now. I get an error: {"error":"ElasticSearchIllegalArgumentException[failed to find analyzer [synonym]]","status":400} which makes sense because the previous call (to create the index) failed. On Tuesday, June 18, 2013 8:18:13 PM UTC-7, Ivan Brusic wrote: > Have you tried using the index in the analysis call? > > [http://localhost:9200/\*testindex\*/\_\*\*analyze?text=this+is+a+test&](http://localhost:9200/*testindex*/_**analyze?text=this+is+a+test&)\*\* > analyzer=synonym[http://localhost:9200/\_analyze?text=this+is+a+test&analyzer=synonym](http://localhost:9200/_analyze?text=this+is+a+test&analyzer=synonym) > > On Tue, Jun 18, 2013 at 8:14 PM, Igal \<[d...@21solutions.net](mailto:d...@21solutions.net) \\>wrote: > > > thanks Ivan, > > > > so how would I map it to a field? > > > > I tried: > > > > PUT /testindex/\_mapping > > { > > "mappings" : { > > "type1" : { > > "properties" : { > > "field1" : { "type" : "string", "analyzer" : "synonym" } > > } > > } > > } > > } > > > > but I get an error 500 -- ElasticSearchIllegalArgumentException: failed > > to find analyzer [synonym] > > > > On Tuesday, June 18, 2013 7:39:09 PM UTC-7, Ivan Brusic wrote: > > > > > You can use a custom analyzer in the Analysis API only after it has been > > > mapped to a field in an index. You don't need to analysis on this field, > > > but the analyzer is not used unless an index that uses it has been created. > > > > > > -- > > > Ivan > > > > > > On Tue, Jun 18, 2013 at 7:03 PM, Igal @ [getRailo.org](http://getRailo.org) \<[ig...@getrailo.org](mailto:ig...@getrailo.org) > > > > > > > wrote: > > > > > > > I define an analyzer in config/elasticsearch.json like so: > > > > > > > > { > > > > "index": { > > > > "analysis": { > > > > "analyzer": { > > > > "synonym": { > > > > "tokenizer": "whitespace", > > > > "filter": ["synonym"] > > > > } > > > > }, > > > > "filter": { > > > > "synonym": { > > > > "type": "synonym", > > > > "synonyms\_path": "synonyms.txt" > > > > } > > > > } > > > > } > > > > } > > > > } > > > > > > > > I know that this part is processed when ES is starting up because when > > > > there is no file at synonyms.txt I see the error in the console and the > > > > error goes away when the file is there -- so far so good. > > > > > > > > it is my understanding that the name of that analyzer is "synonym" > > > > (please correct me if I'm wrong). > > > > > > > > now I'm trying to access that analyzer like so: > > > > > > > > [http://localhost:9200/\_\*\*analyze\*\*?text=this+is+a+test&\*\*analyzer=](http://localhost:9200/_ **analyze**?text=this+is+a+test&**analyzer=)\*\* > > > > synonym[http://localhost:9200/\_analyze?text=this+is+a+test&analyzer=synonym](http://localhost:9200/_analyze?text=this+is+a+test&analyzer=synonym) > > > > > > > > but I get an error 400 - ElasticSearchIllegalArgumentEx\*\*\*\*ception[failed > > > > to find analyzer [synonym]] > > > > > > > > what am I doing wrong? > > > > > > > > TIA, > > > > > > > > Igal > > > > > > > > -- > > > > Igal Sapir > > > > Railo Core Developer > > > > [http://getRailo.org/](http://getRailo.org/) > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to elasticsearc...@ **goog** [legroups.com](http://legroups.com). > > > > > > > > For more options, visit [https://groups.google.com/\*\*grou\*\*ps/opt\_out](https://groups.google.com/ **grou** ps/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > > > > . > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 19, 2013, 7:01am UTC](https://discuss.elastic.co/t/specifying-analyzer/12470/6 "2013-06-19T07:01:09Z")
I think your index is not created with the settings you are expecting. I recommend to use Create Index API: [Elastic — The Search AI Company | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-create-index/) If it does not work, please gist a full curl recreation. [Elastic — The Search AI Company | Elastic](http://www.elasticsearch.org/help/) ## Thanks David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 19 juin 2013 à 05:45, Igal [igal@getrailo.org](mailto:igal@getrailo.org) a écrit : I tried now. I get an error: {"error":"ElasticSearchIllegalArgumentException[failed to find analyzer [synonym]]","status":400} which makes sense because the previous call (to create the index) failed. On Tuesday, June 18, 2013 8:18:13 PM UTC-7, Ivan Brusic wrote: > Have you tried using the index in the analysis call? > > [http://localhost:9200/testindex/\_analyze?text=this+is+a+test&analyzer=synonym](http://localhost:9200/testindex/_analyze?text=this+is+a+test&analyzer=synonym) > > On Tue, Jun 18, 2013 at 8:14 PM, Igal [d...@21solutions.net](mailto:d...@21solutions.net) wrote: > > > thanks Ivan, > > > > so how would I map it to a field? > > > > I tried: > > > > PUT /testindex/\_mapping > > { > > "mappings" : { > > "type1" : { > > "properties" : { > > "field1" : { "type" : "string", "analyzer" : "synonym" } > > } > > } > > } > > } > > > > but I get an error 500 -- ElasticSearchIllegalArgumentException: failed to find analyzer [synonym] > > > > On Tuesday, June 18, 2013 7:39:09 PM UTC-7, Ivan Brusic wrote: > > > > > You can use a custom analyzer in the Analysis API only after it has been mapped to a field in an index. You don't need to analysis on this field, but the analyzer is not used unless an index that uses it has been created. > > > > > > -- > > > Ivan > > > > > > On Tue, Jun 18, 2013 at 7:03 PM, Igal @ [getRailo.org](http://getRailo.org) [ig...@getrailo.org](mailto:ig...@getrailo.org) wrote: > > > > > > > I define an analyzer in config/elasticsearch.json like so: > > > > > > > > { > > > > "index": { > > > > "analysis": { > > > > "analyzer": { > > > > "synonym": { > > > > "tokenizer": "whitespace", > > > > "filter": ["synonym"] > > > > } > > > > }, > > > > "filter": { > > > > "synonym": { > > > > "type": "synonym", > > > > "synonyms\_path": "synonyms.txt" > > > > } > > > > } > > > > } > > > > } > > > > } > > > > > > > > I know that this part is processed when ES is starting up because when there is no file at synonyms.txt I see the error in the console and the error goes away when the file is there -- so far so good. > > > > > > > > it is my understanding that the name of that analyzer is "synonym" (please correct me if I'm wrong). > > > > > > > > now I'm trying to access that analyzer like so: > > > > > > > > [http://localhost:9200/\_analyze?text=this+is+a+test&analyzer=synonym](http://localhost:9200/_analyze?text=this+is+a+test&analyzer=synonym) > > > > > > > > but I get an error 400 - ElasticSearchIllegalArgumentException[failed to find analyzer [synonym]] > > > > > > > > what am I doing wrong? > > > > > > > > TIA, > > > > > > > > Igal > > > > > > > > -- > > > > Igal Sapir > > > > Railo Core Developer > > > > [http://getRailo.org/](http://getRailo.org/) > > > > > > > > -- > > > > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:30am UTC](https://discuss.elastic.co/t/specifying-analyzer/12470/7 "2017-07-06T02:30:29Z")