# Help with soundex/metaphone/synonym query **URL:** \ **Category:** Elasticsearch\ **Created:** [May 28, 2019, 7:32am UTC](https://discuss.elastic.co/t/help-with-soundex-metaphone-synonym-query/183010 "2019-05-28T07:32:16Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mikeq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikeq/32/46931_2.png) [@mikeq](https://discuss.elastic.co/u/mikeq)\ **Post date:** [May 28, 2019, 7:32am UTC](https://discuss.elastic.co/t/help-with-soundex-metaphone-synonym-query/183010/1 "2019-05-28T07:32:16Z")
Hi, Struggling to get a particular query working. We have a single search bar where a user could type in various terms to search for related to people, i.e. "john smith manager edinburgh" and the following query works okay for this ``` GET myindex/_search { "query": { "multi_match": { "query": "john smith manager edinburgh", "fields": [ "first_name", "last_name", "post_code", "post_town", "place_of_birth", "known_as", "maiden_name", "occupation", "date_of_birth.text", "address", "contact_details.telephone.value" ], "type": "cross_fields", "operator": "and" } } } ``` There is a requirement to use phonetics on the surname, so have defined an appropriate analyzer for the last\_name, when applying this to the query ``` GET myindex/_search { "query": { "multi_match": { "query": "john smith manager edinburgh", "fields": [ "first_name", "last_name.metaphone", "post_code", "post_town", "place_of_birth", "known_as", "maiden_name", "occupation", "date_of_birth.text", "address", "contact_details.telephone.value" ], "type": "cross_fields", "operator": "and" } } } ``` Returns no hits, whereas the previous query returned 1 hit. just searching on say "smith" or "smyth" or "smythe" work as I would expect all return the same hits regardless of the spelling of smith. We also have declared a synonym analyzer for first\_name so that when say a user enters "jim" it also searches for "james, jamie, jimmy, jimmie" for example. But again the same issue applies that when applying the search to first\_name.syn it doesn't work ``` GET myindex/_search { "query": { "multi_match": { "query": "james evans", "fields": [ "first_name.syn", "last_name", "post_code", "post_town", "place_of_birth", "known_as", "maiden_name", "occupation", "date_of_birth.text", "address", "contact_details.telephone.value" ], "type": "cross_fields", "operator": "and" } } } ``` would return 1 hit, but searching "jim evans" doesn't return any hits and I know the synonyms and applied to the field, I would expect "jim evans" to return the exact same hit ``` GET myindex/_analyze { "analyzer": "synonym_analyzer", "text": "james" } ``` produces ``` { "tokens" : [ { "token" : "james", "start_offset" : 0, "end_offset" : 5, "type" : "", "position" : 0 }, { "token" : "jamie", "start_offset" : 0, "end_offset" : 5, "type" : "SYNONYM", "position" : 0 }, { "token" : "jem", "start_offset" : 0, "end_offset" : 5, "type" : "SYNONYM", "position" : 0 }, { "token" : "jim", "start_offset" : 0, "end_offset" : 5, "type" : "SYNONYM", "position" : 0 }, { "token" : "jimmie", "start_offset" : 0, "end_offset" : 5, "type" : "SYNONYM", "position" : 0 }, { "token" : "jimmy", "start_offset" : 0, "end_offset" : 5, "type" : "SYNONYM", "position" : 0 } ] } ``` filters and analyzers defined as ``` "settings": { "number_of_shards": 1, "number_of_replicas": 0, "index": { "analysis": { "analyzer": { "synonym_analyzer": { "tokenizer": "standard", "filter": ["lowercase", "synonym"] }, "lookahead_analyzer": { "type": "custom", "tokenizer": "standard", "filter": ["lowercase", "custom_edge_ngram"] }, "nospaces_analyzer": { "type": "custom", "tokenizer": "keyword", "filter": ["lowercase", "whitespace_remove"] }, "nospaces_edgengram_analyzer": { "type": "custom", "tokenizer": "keyword", "filter": ["lowercase", "whitespace_remove", "custom_edge_ngram"] }, "metaphone_analyzer": { "tokenizer": "standard", "filter": ["lowercase", "insight_metaphone"] }, "soundex_analyzer": { "tokenizer": "standard", "filter": ["lowercase", "insight_soundex"] } }, "filter": { "custom_edge_ngram": { "type": "edge_ngram", "min_gram": 2, "max_gram": 10 }, "synonym": { "type": "synonym", "expand": true, "synonyms_path": "/usr/share/elasticsearch/config/fixed.syn" }, "whitespace_remove": { "type": "pattern_replace", "pattern": " ", "replacement": "" }, "insight_metaphone": { "type": "phonetic", "encoder": "metaphone", "replace": false }, "insight_soundex": { "type": "phonetic", "encoder": "soundex", "replace": false } } } } }, ``` At a loss as to how to structure the query properly, any help would be appreciated Thanks Mike ---
**Author:** ![mikeq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikeq/32/46931_2.png) [@mikeq](https://discuss.elastic.co/u/mikeq)\ **Post date:** [June 6, 2019, 3:35pm UTC](https://discuss.elastic.co/t/help-with-soundex-metaphone-synonym-query/183010/2 "2019-06-06T15:35:24Z")
Oh well. I guess it's just too complicated for y'all ---
**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\ **Post date:** [June 6, 2019, 3:46pm UTC](https://discuss.elastic.co/t/help-with-soundex-metaphone-synonym-query/183010/3 "2019-06-06T15:46:53Z")
Hi Mike, Sorry it's taken a while for any response. I haven't got time to take a closer look at the moment but one limitation to consider here is that cross-fields relies on fields sharing the same analyzer because given identical token streams it needs to balance the doc frequencies reported across each field. If you have different analyzers then you have different tokens and any notion of frequency balancing goes out the window because fields fundamentally disagree on which tokens are being assessed. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 4, 2019, 3:55pm UTC](https://discuss.elastic.co/t/help-with-soundex-metaphone-synonym-query/183010/4 "2019-07-04T15:55:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.