# Wrestling with analyzer **URL:** \ **Category:** Elasticsearch\ **Created:** [July 31, 2013, 2:19pm UTC](https://discuss.elastic.co/t/wrestling-with-analyzer/13014 "2013-07-31T14:19:04Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Joost\_Cassee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joost_cassee/32/2156_2.png) [@Joost\_Cassee](https://discuss.elastic.co/u/Joost_Cassee)\ **Post date:** [July 31, 2013, 2:19pm UTC](https://discuss.elastic.co/t/wrestling-with-analyzer/13014/1 "2013-07-31T14:19:04Z")
Hi, At Go About we are using elasticsearch (0.90.2) for geocoding. Unfortunately, I am running into a problem I could use some help with. I use the following analyzer configuration: index: analysis: analyzer: default: alias: [goabout] type: custom tokenizer: standard filter: [lowercase, synonym, standard, asciifolding] char\_filter: [char\_mapper] postal\_code: tokenizer: keyword filter: [lowercase] tokenizer: standard: stopwords: [] filter: synonym: type: synonym synonyms: - st =\> sint - den haag =\> s gravenhage - den bosch =\> s hertogenbosch - jp =\> jan pieterszoon - mh =\> maarten harpertszoon char\_filter: char\_mapper: type: mapping mappings: - ij =\> y I then the index the following document: $ curl -XPUT [http://localhost:9200/geocoder/address/1](http://localhost:9200/geocoder/address/1) -d "{"city": "'s-Gravenhage", "point": {"lat": 52.034608082483366, "lon": 4.266201580347966}, "street": "Wantsnijdersgaarde", "postal\_code": "2542 GN", "housenumber": "573"}" (We put a mapping first to make sure "point" is a geo\_point, but this is not relevant for this problem.) The analyzer seems to work correctly: $ curl -X GET "[http://localhost:9200/geocoder/\_analyze?pretty=true](http://localhost:9200/geocoder/_analyze?pretty=true)" -d "Den Haag" { "tokens" : [ { "token" : "s", "start\_offset" : 0, "end\_offset" : 3, "type" : "SYNONYM", "position" : 1 }, { "token" : "gravenhage", "start\_offset" : 4, "end\_offset" : 8, "type" : "SYNONYM", "position" : 2 } ] } The analyzer seems to get use in both indexing and querying, as this query (that exchanges "y" for "ij") finds the document: $ curl -X GET "[http://localhost:9200/geocoder/\_search?q=Wantsnydersgaarde&analyzer=goabout&pretty=true](http://localhost:9200/geocoder/_search?q=Wantsnydersgaarde&analyzer=goabout&pretty=true)" { "took" : 5, "timed\_out" : false, "\_shards" : { "total" : 5, "successful" : 5, "failed" : 0 }, "hits" : { "total" : 1, "max\_score" : 0.095891505, "hits" : [ { "\_index" : "geocoder", "\_type" : "address", "\_id" : "1", "\_score" : 0.095891505, "\_source" : {"city": "'s-Gravenhage", "point": {"lat": 52.034608082483366, "lon": 4.266201580347966}, "street": "Wantsnijdersgaarde", "postal\_code": "2542 GN", "housenumber": "573"} } ] } } But this search query does not return results: $ curl -X GET "[http://localhost:9200/geocoder/\_search?q=den+haag&analyzer=goabout&pretty=true](http://localhost:9200/geocoder/_search?q=den+haag&analyzer=goabout&pretty=true)" { "took" : 5, "timed\_out" : false, "\_shards" : { "total" : 5, "successful" : 5, "failed" : 0 }, "hits" : { "total" : 0, "max\_score" : null, "hits" : [] } } Something is going on with the synonym filter. What can I do to further debug my problem? Regards, Joost -- 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:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [August 2, 2013, 8:13pm UTC](https://discuss.elastic.co/t/wrestling-with-analyzer/13014/2 "2013-08-02T20:13:10Z")
Can you send your mapping as well? Maybe you don't set the index / search analyzer for the field "city" in the mapping. if you don't you won't use the syn. filter there. simon On Wednesday, July 31, 2013 4:19:04 PM UTC+2, Joost Cassee wrote: > Hi, > > At Go About we are using elasticsearch (0.90.2) for geocoding. > Unfortunately, I am running into a problem I could use some help with. > > I use the following analyzer configuration: > > index: > analysis: > analyzer: > default: > alias: [goabout] > type: custom > tokenizer: standard > filter: [lowercase, synonym, standard, asciifolding] > char\_filter: [char\_mapper] > postal\_code: > tokenizer: keyword > filter: [lowercase] > tokenizer: > standard: > stopwords: > filter: > synonym: > type: synonym > synonyms: > - st =\> sint > - den haag =\> s gravenhage > - den bosch =\> s hertogenbosch > - jp =\> jan pieterszoon > - mh =\> maarten harpertszoon > char\_filter: > char\_mapper: > type: mapping > mappings: > - ij =\> y > > I then the index the following document: > > $ curl -XPUT [http://localhost:9200/geocoder/address/1](http://localhost:9200/geocoder/address/1) -d "{"city": > "'s-Gravenhage", "point": {"lat": 52.034608082483366, "lon": > 4.266201580347966}, "street": "Wantsnijdersgaarde", "postal\_code": > "2542 GN", "housenumber": "573"}" > > (We put a mapping first to make sure "point" is a geo\_point, but this is > not relevant for this problem.) > > The analyzer seems to work correctly: > > $ curl -X GET "[http://localhost:9200/geocoder/\_analyze?pretty=true](http://localhost:9200/geocoder/_analyze?pretty=true)" -d > "Den Haag" > { > "tokens" : [ { > "token" : "s", > "start\_offset" : 0, > "end\_offset" : 3, > "type" : "SYNONYM", > "position" : 1 > }, { > "token" : "gravenhage", > "start\_offset" : 4, > "end\_offset" : 8, > "type" : "SYNONYM", > "position" : 2 > } ] > } > > The analyzer seems to get use in both indexing and querying, as this query > (that exchanges "y" for "ij") finds the document: > > $ curl -X GET " > [http://localhost:9200/geocoder/\_search?q=Wantsnydersgaarde&analyzer=goabout&pretty=true](http://localhost:9200/geocoder/_search?q=Wantsnydersgaarde&analyzer=goabout&pretty=true)" > > { > "took" : 5, > "timed\_out" : false, > "\_shards" : { > "total" : 5, > "successful" : 5, > "failed" : 0 > }, > "hits" : { > "total" : 1, > "max\_score" : 0.095891505, > "hits" : [ { > "\_index" : "geocoder", > "\_type" : "address", > "\_id" : "1", > "\_score" : 0.095891505, "\_source" : {"city": "'s-Gravenhage", > "point": {"lat": 52.034608082483366, "lon": 4.266201580347966}, "street": > "Wantsnijdersgaarde", "postal\_code": "2542 GN", "housenumber": "573"} > } ] > } > } > > But this search query does not return results: > > $ curl -X GET " > [http://localhost:9200/geocoder/\_search?q=den+haag&analyzer=goabout&pretty=true](http://localhost:9200/geocoder/_search?q=den+haag&analyzer=goabout&pretty=true)" > > { > "took" : 5, > "timed\_out" : false, > "\_shards" : { > "total" : 5, > "successful" : 5, > "failed" : 0 > }, > "hits" : { > "total" : 0, > "max\_score" : null, > "hits" : > } > } > > Something is going on with the synonym filter. What can I do to further > debug my problem? > > Regards, > Joost -- 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:** ![Joost\_Cassee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joost_cassee/32/2156_2.png) [@Joost\_Cassee](https://discuss.elastic.co/u/Joost_Cassee)\ **Post date:** [August 5, 2013, 10:19am UTC](https://discuss.elastic.co/t/wrestling-with-analyzer/13014/3 "2013-08-05T10:19:24Z")
Hi Simon, This is the mapping for the address type: { "properties": { "street": { "type": "string" }, "housenumber": { "type": "string" }, "postal\_code": { "type": "string", "analyzer": "postal\_code" }, "city": { "type": "string" }, "point": { "type": "geo\_point" } } } I expected the city field to be analyzed by the default analyzer, which is the one I configured, right? Regards, Joost 2013/8/2 simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com): > Can you send your mapping as well? Maybe you don't set the index / search > analyzer for the field "city" in the mapping. if you don't you won't use the > syn. filter there. > > simon > > On Wednesday, July 31, 2013 4:19:04 PM UTC+2, Joost Cassee wrote: > > > Hi, > > > > At Go About we are using elasticsearch (0.90.2) for geocoding. > > Unfortunately, I am running into a problem I could use some help with. > > > > I use the following analyzer configuration: > > > > index: > > analysis: > > analyzer: > > default: > > alias: [goabout] > > type: custom > > tokenizer: standard > > filter: [lowercase, synonym, standard, asciifolding] > > char\_filter: [char\_mapper] > > postal\_code: > > tokenizer: keyword > > filter: [lowercase] > > tokenizer: > > standard: > > stopwords: > > filter: > > synonym: > > type: synonym > > synonyms: > > - st =\> sint > > - den haag =\> s gravenhage > > - den bosch =\> s hertogenbosch > > - jp =\> jan pieterszoon > > - mh =\> maarten harpertszoon > > char\_filter: > > char\_mapper: > > type: mapping > > mappings: > > - ij =\> y > > > > I then the index the following document: > > > > $ curl -XPUT [http://localhost:9200/geocoder/address/1](http://localhost:9200/geocoder/address/1) -d "{"city": > > "'s-Gravenhage", "point": {"lat": 52.034608082483366, "lon": > > 4.266201580347966}, "street": "Wantsnijdersgaarde", "postal\_code": > > "2542 GN", "housenumber": "573"}" > > > > (We put a mapping first to make sure "point" is a geo\_point, but this is > > not relevant for this problem.) > > > > The analyzer seems to work correctly: > > > > $ curl -X GET "[http://localhost:9200/geocoder/\_analyze?pretty=true](http://localhost:9200/geocoder/_analyze?pretty=true)" -d > > "Den Haag" > > { > > "tokens" : [ { > > "token" : "s", > > "start\_offset" : 0, > > "end\_offset" : 3, > > "type" : "SYNONYM", > > "position" : 1 > > }, { > > "token" : "gravenhage", > > "start\_offset" : 4, > > "end\_offset" : 8, > > "type" : "SYNONYM", > > "position" : 2 > > } ] > > } > > > > The analyzer seems to get use in both indexing and querying, as this query > > (that exchanges "y" for "ij") finds the document: > > > > $ curl -X GET > > "[http://localhost:9200/geocoder/\_search?q=Wantsnydersgaarde&analyzer=goabout&pretty=true](http://localhost:9200/geocoder/_search?q=Wantsnydersgaarde&analyzer=goabout&pretty=true)" > > { > > "took" : 5, > > "timed\_out" : false, > > "\_shards" : { > > "total" : 5, > > "successful" : 5, > > "failed" : 0 > > }, > > "hits" : { > > "total" : 1, > > "max\_score" : 0.095891505, > > "hits" : [ { > > "\_index" : "geocoder", > > "\_type" : "address", > > "\_id" : "1", > > "\_score" : 0.095891505, "\_source" : {"city": "'s-Gravenhage", > > "point": {"lat": 52.034608082483366, "lon": 4.266201580347966}, "street": > > "Wantsnijdersgaarde", "postal\_code": "2542 GN", "housenumber": "573"} > > } ] > > } > > } > > > > But this search query does not return results: > > > > $ curl -X GET > > "[http://localhost:9200/geocoder/\_search?q=den+haag&analyzer=goabout&pretty=true](http://localhost:9200/geocoder/_search?q=den+haag&analyzer=goabout&pretty=true)" > > { > > "took" : 5, > > "timed\_out" : false, > > "\_shards" : { > > "total" : 5, > > "successful" : 5, > > "failed" : 0 > > }, > > "hits" : { > > "total" : 0, > > "max\_score" : null, > > "hits" : > > } > > } > > > > Something is going on with the synonym filter. What can I do to further > > debug my problem? > > > > Regards, > > Joost > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/NHR4uRa0y8E/unsubscribe](https://groups.google.com/d/topic/elasticsearch/NHR4uRa0y8E/unsubscribe). > To unsubscribe from this group and all its topics, 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). -- Joost Cassee [http://joost.cassee.net](http://joost.cassee.net) -- 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:** ![Joost\_Cassee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joost_cassee/32/2156_2.png) [@Joost\_Cassee](https://discuss.elastic.co/u/Joost_Cassee)\ **Post date:** [August 5, 2013, 1:05pm UTC](https://discuss.elastic.co/t/wrestling-with-analyzer/13014/4 "2013-08-05T13:05:49Z")
After some digging I found a way to show the indexed terms, and the analyzer has performed the "ij" -\> "y" mapping: $ curl '[http://localhost:9200/geocoder/\_search?pretty=true](http://localhost:9200/geocoder/_search?pretty=true)' -d '{ "query" : { "match\_all" : { } }, "script\_fields": { "terms" : { "script": "doc[field].values", "params": { "field": "\_all" } } ``` } ``` }' { "took" : 10, "timed\_out" : false, "\_shards" : { "total" : 5, "successful" : 5, "failed" : 0 }, "hits" : { "total" : 1, "max\_score" : 1.0, "hits" : [ { "\_index" : "geocoder", "\_type" : "address", "\_id" : "1", "\_score" : 1.0, "fields" : { "terms" : [ "2542", "573", "gn", "gravenhage", "s", "wantsnydersgaarde" ] } } ] } } Can anything else go wrong with the mapping? Regards, Joost 2013/8/5 Joost Cassee [joost@cassee.net](mailto:joost@cassee.net): > Hi Simon, > > This is the mapping for the address type: > > { > "properties": { > "street": { "type": "string" }, > "housenumber": { "type": "string" }, > "postal\_code": { "type": "string", "analyzer": "postal\_code" }, > "city": { "type": "string" }, > "point": { "type": "geo\_point" } > } > } > > I expected the city field to be analyzed by the default analyzer, > which is the one I configured, right? > > Regards, > Joost > > 2013/8/2 simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com): > > > Can you send your mapping as well? Maybe you don't set the index / search > > analyzer for the field "city" in the mapping. if you don't you won't use the > > syn. filter there. > > > > simon > > > > On Wednesday, July 31, 2013 4:19:04 PM UTC+2, Joost Cassee wrote: > > > > > Hi, > > > > > > At Go About we are using elasticsearch (0.90.2) for geocoding. > > > Unfortunately, I am running into a problem I could use some help with. > > > > > > I use the following analyzer configuration: > > > > > > index: > > > analysis: > > > analyzer: > > > default: > > > alias: [goabout] > > > type: custom > > > tokenizer: standard > > > filter: [lowercase, synonym, standard, asciifolding] > > > char\_filter: [char\_mapper] > > > postal\_code: > > > tokenizer: keyword > > > filter: [lowercase] > > > tokenizer: > > > standard: > > > stopwords: > > > filter: > > > synonym: > > > type: synonym > > > synonyms: > > > - st =\> sint > > > - den haag =\> s gravenhage > > > - den bosch =\> s hertogenbosch > > > - jp =\> jan pieterszoon > > > - mh =\> maarten harpertszoon > > > char\_filter: > > > char\_mapper: > > > type: mapping > > > mappings: > > > - ij =\> y > > > > > > I then the index the following document: > > > > > > $ curl -XPUT [http://localhost:9200/geocoder/address/1](http://localhost:9200/geocoder/address/1) -d "{"city": > > > "'s-Gravenhage", "point": {"lat": 52.034608082483366, "lon": > > > 4.266201580347966}, "street": "Wantsnijdersgaarde", "postal\_code": > > > "2542 GN", "housenumber": "573"}" > > > > > > (We put a mapping first to make sure "point" is a geo\_point, but this is > > > not relevant for this problem.) > > > > > > The analyzer seems to work correctly: > > > > > > $ curl -X GET "[http://localhost:9200/geocoder/\_analyze?pretty=true](http://localhost:9200/geocoder/_analyze?pretty=true)" -d > > > "Den Haag" > > > { > > > "tokens" : [ { > > > "token" : "s", > > > "start\_offset" : 0, > > > "end\_offset" : 3, > > > "type" : "SYNONYM", > > > "position" : 1 > > > }, { > > > "token" : "gravenhage", > > > "start\_offset" : 4, > > > "end\_offset" : 8, > > > "type" : "SYNONYM", > > > "position" : 2 > > > } ] > > > } > > > > > > The analyzer seems to get use in both indexing and querying, as this query > > > (that exchanges "y" for "ij") finds the document: > > > > > > $ curl -X GET > > > "[http://localhost:9200/geocoder/\_search?q=Wantsnydersgaarde&analyzer=goabout&pretty=true](http://localhost:9200/geocoder/_search?q=Wantsnydersgaarde&analyzer=goabout&pretty=true)" > > > { > > > "took" : 5, > > > "timed\_out" : false, > > > "\_shards" : { > > > "total" : 5, > > > "successful" : 5, > > > "failed" : 0 > > > }, > > > "hits" : { > > > "total" : 1, > > > "max\_score" : 0.095891505, > > > "hits" : [ { > > > "\_index" : "geocoder", > > > "\_type" : "address", > > > "\_id" : "1", > > > "\_score" : 0.095891505, "\_source" : {"city": "'s-Gravenhage", > > > "point": {"lat": 52.034608082483366, "lon": 4.266201580347966}, "street": > > > "Wantsnijdersgaarde", "postal\_code": "2542 GN", "housenumber": "573"} > > > } ] > > > } > > > } > > > > > > But this search query does not return results: > > > > > > $ curl -X GET > > > "[http://localhost:9200/geocoder/\_search?q=den+haag&analyzer=goabout&pretty=true](http://localhost:9200/geocoder/_search?q=den+haag&analyzer=goabout&pretty=true)" > > > { > > > "took" : 5, > > > "timed\_out" : false, > > > "\_shards" : { > > > "total" : 5, > > > "successful" : 5, > > > "failed" : 0 > > > }, > > > "hits" : { > > > "total" : 0, > > > "max\_score" : null, > > > "hits" : > > > } > > > } > > > > > > Something is going on with the synonym filter. What can I do to further > > > debug my problem? > > > > > > Regards, > > > Joost > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/NHR4uRa0y8E/unsubscribe](https://groups.google.com/d/topic/elasticsearch/NHR4uRa0y8E/unsubscribe). > > To unsubscribe from this group and all its topics, 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). > > -- > Joost Cassee > [http://joost.cassee.net](http://joost.cassee.net) -- Joost Cassee [http://joost.cassee.net](http://joost.cassee.net) -- 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:** ![Joost\_Cassee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joost_cassee/32/2156_2.png) [@Joost\_Cassee](https://discuss.elastic.co/u/Joost_Cassee)\ **Post date:** [August 17, 2013, 11:49pm UTC](https://discuss.elastic.co/t/wrestling-with-analyzer/13014/5 "2013-08-17T23:49:11Z")
In GitHub issue 3494, Igor Motov wrote: > In order to find operators, the query string parser is using spaces > to split query string first and only then it passes each part through > analyzer to produce token. Your query is basically equivalent to the > query "den OR haag": > > $ curl -XGET "[http://localhost:9200/geocoder/\_validate/query?q=den+haag&analyzer=goabout&pretty=true&explain=true](http://localhost:9200/geocoder/_validate/query?q=den+haag&analyzer=goabout&pretty=true&explain=true)" > { > "valid" : true, > "\_shards" : { > "total" : 1, > "successful" : 1, > "failed" : 0 > }, > "explanations" : [ { > "index" : "test-idx", > "valid" : true, > "explanation" : "\_all:den \_all:haag" > } ] > } Thanks for clearing that up! > If you are not going to use any query string query operators, > I would suggest using match query instead of query string query. Actually, I was initially going to use a match\_phrase\_prefix query, but the problem is I want to be able to match across fields: $ curl -XGET "[http://localhost:9200/geocoder/\_search/?pretty=true](http://localhost:9200/geocoder/_search/?pretty=true)" -d '{ "query": { "match\_phrase\_prefix": { "\_all": { "query": "573 wantsn" } } } }' { "took" : 2, "timed\_out" : false, "\_shards" : { "total" : 5, "successful" : 5, "failed" : 0 }, "hits" : { "total" : 0, "max\_score" : null, "hits" : } } Als, matching the prefix of a synonym does not work. (For example doing a match\_phrase\_prefix query for "den haa" gives no hits.) That is why I started using the query\_string query. But maybe there is another technique for doing this. Regards, Joost 2013/8/5 Joost Cassee [joost@cassee.net](mailto:joost@cassee.net): > After some digging I found a way to show the indexed terms, and the > analyzer has performed the "ij" -\> "y" mapping: > > $ curl '[http://localhost:9200/geocoder/\_search?pretty=true](http://localhost:9200/geocoder/_search?pretty=true)' -d '{ > "query" : { > "match\_all" : { } > }, > "script\_fields": { > "terms" : { > "script": "doc[field].values", > "params": { > "field": "\_all" > } > } > > ``` > } > > ``` > > }' > { > "took" : 10, > "timed\_out" : false, > "\_shards" : { > "total" : 5, > "successful" : 5, > "failed" : 0 > }, > "hits" : { > "total" : 1, > "max\_score" : 1.0, > "hits" : [ { > "\_index" : "geocoder", > "\_type" : "address", > "\_id" : "1", > "\_score" : 1.0, > "fields" : { > "terms" : [ "2542", "573", "gn", "gravenhage", "s", > "wantsnydersgaarde" ] > } > } ] > } > } > > Can anything else go wrong with the mapping? > > Regards, > Joost > > 2013/8/5 Joost Cassee [joost@cassee.net](mailto:joost@cassee.net): > > > Hi Simon, > > > > This is the mapping for the address type: > > > > { > > "properties": { > > "street": { "type": "string" }, > > "housenumber": { "type": "string" }, > > "postal\_code": { "type": "string", "analyzer": "postal\_code" }, > > "city": { "type": "string" }, > > "point": { "type": "geo\_point" } > > } > > } > > > > I expected the city field to be analyzed by the default analyzer, > > which is the one I configured, right? > > > > Regards, > > Joost > > > > 2013/8/2 simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com): > > > > > Can you send your mapping as well? Maybe you don't set the index / search > > > analyzer for the field "city" in the mapping. if you don't you won't use the > > > syn. filter there. > > > > > > simon > > > > > > On Wednesday, July 31, 2013 4:19:04 PM UTC+2, Joost Cassee wrote: > > > > > > > Hi, > > > > > > > > At Go About we are using elasticsearch (0.90.2) for geocoding. > > > > Unfortunately, I am running into a problem I could use some help with. > > > > > > > > I use the following analyzer configuration: > > > > > > > > index: > > > > analysis: > > > > analyzer: > > > > default: > > > > alias: [goabout] > > > > type: custom > > > > tokenizer: standard > > > > filter: [lowercase, synonym, standard, asciifolding] > > > > char\_filter: [char\_mapper] > > > > postal\_code: > > > > tokenizer: keyword > > > > filter: [lowercase] > > > > tokenizer: > > > > standard: > > > > stopwords: > > > > filter: > > > > synonym: > > > > type: synonym > > > > synonyms: > > > > - st =\> sint > > > > - den haag =\> s gravenhage > > > > - den bosch =\> s hertogenbosch > > > > - jp =\> jan pieterszoon > > > > - mh =\> maarten harpertszoon > > > > char\_filter: > > > > char\_mapper: > > > > type: mapping > > > > mappings: > > > > - ij =\> y > > > > > > > > I then the index the following document: > > > > > > > > $ curl -XPUT [http://localhost:9200/geocoder/address/1](http://localhost:9200/geocoder/address/1) -d "{"city": > > > > "'s-Gravenhage", "point": {"lat": 52.034608082483366, "lon": > > > > 4.266201580347966}, "street": "Wantsnijdersgaarde", "postal\_code": > > > > "2542 GN", "housenumber": "573"}" > > > > > > > > (We put a mapping first to make sure "point" is a geo\_point, but this is > > > > not relevant for this problem.) > > > > > > > > The analyzer seems to work correctly: > > > > > > > > $ curl -X GET "[http://localhost:9200/geocoder/\_analyze?pretty=true](http://localhost:9200/geocoder/_analyze?pretty=true)" -d > > > > "Den Haag" > > > > { > > > > "tokens" : [ { > > > > "token" : "s", > > > > "start\_offset" : 0, > > > > "end\_offset" : 3, > > > > "type" : "SYNONYM", > > > > "position" : 1 > > > > }, { > > > > "token" : "gravenhage", > > > > "start\_offset" : 4, > > > > "end\_offset" : 8, > > > > "type" : "SYNONYM", > > > > "position" : 2 > > > > } ] > > > > } > > > > > > > > The analyzer seems to get use in both indexing and querying, as this query > > > > (that exchanges "y" for "ij") finds the document: > > > > > > > > $ curl -X GET > > > > "[http://localhost:9200/geocoder/\_search?q=Wantsnydersgaarde&analyzer=goabout&pretty=true](http://localhost:9200/geocoder/_search?q=Wantsnydersgaarde&analyzer=goabout&pretty=true)" > > > > { > > > > "took" : 5, > > > > "timed\_out" : false, > > > > "\_shards" : { > > > > "total" : 5, > > > > "successful" : 5, > > > > "failed" : 0 > > > > }, > > > > "hits" : { > > > > "total" : 1, > > > > "max\_score" : 0.095891505, > > > > "hits" : [ { > > > > "\_index" : "geocoder", > > > > "\_type" : "address", > > > > "\_id" : "1", > > > > "\_score" : 0.095891505, "\_source" : {"city": "'s-Gravenhage", > > > > "point": {"lat": 52.034608082483366, "lon": 4.266201580347966}, "street": > > > > "Wantsnijdersgaarde", "postal\_code": "2542 GN", "housenumber": "573"} > > > > } ] > > > > } > > > > } > > > > > > > > But this search query does not return results: > > > > > > > > $ curl -X GET > > > > "[http://localhost:9200/geocoder/\_search?q=den+haag&analyzer=goabout&pretty=true](http://localhost:9200/geocoder/_search?q=den+haag&analyzer=goabout&pretty=true)" > > > > { > > > > "took" : 5, > > > > "timed\_out" : false, > > > > "\_shards" : { > > > > "total" : 5, > > > > "successful" : 5, > > > > "failed" : 0 > > > > }, > > > > "hits" : { > > > > "total" : 0, > > > > "max\_score" : null, > > > > "hits" : > > > > } > > > > } > > > > > > > > Something is going on with the synonym filter. What can I do to further > > > > debug my problem? > > > > > > > > Regards, > > > > Joost > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/NHR4uRa0y8E/unsubscribe](https://groups.google.com/d/topic/elasticsearch/NHR4uRa0y8E/unsubscribe). > > > To unsubscribe from this group and all its topics, 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). > > > > -- > > Joost Cassee > > [http://joost.cassee.net](http://joost.cassee.net) > > -- > Joost Cassee > [http://joost.cassee.net](http://joost.cassee.net) -- Joost Cassee [http://joost.cassee.net](http://joost.cassee.net) -- 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:20am UTC](https://discuss.elastic.co/t/wrestling-with-analyzer/13014/6 "2017-07-06T02:20:43Z")