# Completion suggestions with strings containing only numbers and strings prefixed with numbers (e.g. addresses) not working **URL:** \ **Category:** Elasticsearch\ **Created:** [November 21, 2013, 7:07pm UTC](https://discuss.elastic.co/t/completion-suggestions-with-strings-containing-only-numbers-and-strings-prefixed-with-numbers-e-g-addresses-not-working/14523 "2013-11-21T19:07:02Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Mahesh\_Kommareddi](https://avatars.discourse-cdn.com/v4/letter/m/bcef8e/32.png) [@Mahesh\_Kommareddi](https://discuss.elastic.co/u/Mahesh_Kommareddi)\ **Post date:** [November 21, 2013, 7:07pm UTC](https://discuss.elastic.co/t/completion-suggestions-with-strings-containing-only-numbers-and-strings-prefixed-with-numbers-e-g-addresses-not-working/14523/1 "2013-11-21T19:07:02Z")
Hi, I'm using and testing against 0.90.5 (three nodes and five shards) and 0.90.7 (one node and five shards). I'm interested in the completion suggester and it works great for items where letters are involved. For example, first names, last names, states, cities, or product names all return suggestions. This is with the help of the documentation that is on the Elasticsearch website: [http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-suggesters-completion.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-suggesters-completion.html) As an example, I created a 'numbers' index with a type named 'zipcode'. The stored document contains a field that is a string: > I receive: {"ok":true,"acknowledged":true} Next, I insert some zipcodes as strings: > I receive: {"ok":true,"\_index":"numbers","\_type":"zipcode","\_id":"1","\_version":1} {"ok":true,"\_index":"numbers","\_type":"zipcode","\_id":"2","\_version":1} Now the suggestion: > I expect the "90210" string to be returned. However, I get no result: { "\_shards" : { "total" : 5, "successful" : 5, "failed" : 0 }, "numbers-suggest" : [ { "text" : "902", "offset" : 0, "length" : 3, "options" : [] } ] } Just to be sure, I insert an item that contains alphabetical items only and query for a suggestion: > Which returns a result as expected: { "\_shards" : { "total" : 5, "successful" : 5, "failed" : 0 }, "numbers-suggest" : [ { "text" : "bl", "offset" : 0, "length" : 2, "options" : [ { "text" : "Blah blah", "score" : 1.0, "payload" : {"area code":0} } ] } ] } It appears that zipcodes ("90210", "29268", "28262"), phone numbers ("7042315555", "5555555555", 9999999999"), and addresses starting with numbers ("123 Rose Ln", "111 White St", etc) are not suggested even though all these items are stored as strings. Is this a limitation? If so, is there a way around it? Thanks, Mahesh -- 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:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [November 22, 2013, 8:24am UTC](https://discuss.elastic.co/t/completion-suggestions-with-strings-containing-only-numbers-and-strings-prefixed-with-numbers-e-g-addresses-not-working/14523/2 "2013-11-22T08:24:39Z")
Hey, try running the analyze API for numbers using the simple analyzer and compare it with the output of the standard analyzer » curl 'localhost:9200/\_analyze?analyzer=standard' -d '12345' {"tokens":[{"token":"12345","start\_offset":0,"end\_offset":5,"type":"","position":1}]} » curl 'localhost:9200/\_analyze?analyzer=simple' -d '12345' {"tokens":} as you can see, the simple analyzer actually removed the numbers. So most likely the simple analyzer is not useful to return numbers in your case and you should stick with another analyzer, as the simple analyzer removes any numbers - which explains you not getting any results. --Alex On Thu, Nov 21, 2013 at 8:07 PM, Mahesh Kommareddi \< [mahesh.kommareddi@gmail.com](mailto:mahesh.kommareddi@gmail.com)\> wrote: > Hi, > I'm using and testing against 0.90.5 (three nodes and five shards) and > 0.90.7 (one node and five shards). I'm interested in the completion > suggester and it works great for items where letters are involved. For > example, first names, last names, states, cities, or product names all > return suggestions. This is with the help of the documentation that is on > the Elasticsearch website: > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-suggesters-completion.html) > > As an example, I created a 'numbers' index with a type named 'zipcode'. > The stored document contains a field that is a string: > [Creation of a mapping for zipcodes · GitHub](https://gist.github.com/mkommar/7586804) > > I receive: {"ok":true,"acknowledged":true} > > Next, I insert some zipcodes as strings: > [Adding document to the type · GitHub](https://gist.github.com/mkommar/7586857) > > I receive: > {"ok":true,"\_index":"numbers","\_type":"zipcode","\_id":"1","\_version":1} > {"ok":true,"\_index":"numbers","\_type":"zipcode","\_id":"2","\_version":1} > > Now the suggestion: > [Asking for a suggestion based on one of the inputted documents. · GitHub](https://gist.github.com/mkommar/7587131) > > I expect the "90210" string to be returned. However, I get no result: > { > "\_shards" : { > "total" : 5, > "successful" : 5, > "failed" : 0 > }, > "numbers-suggest" : [ { > "text" : "902", > "offset" : 0, > "length" : 3, > "options" : > } ] > } > > Just to be sure, I insert an item that contains alphabetical items only > and query for a suggestion: > [Adding a non-numeric item and asking for a suggestion · GitHub](https://gist.github.com/mkommar/7587188) > > Which returns a result as expected: > { > "\_shards" : { > "total" : 5, > "successful" : 5, > "failed" : 0 > }, > "numbers-suggest" : [ { > "text" : "bl", > "offset" : 0, > "length" : 2, > "options" : [ { > "text" : "Blah blah", > "score" : 1.0, "payload" : {"area code":0} > } ] > } ] > } > > It appears that zipcodes ("90210", "29268", "28262"), phone numbers (" > 7042315555", "5555555555", 9999999999"), and addresses starting with > numbers ("123 Rose Ln", "111 White St", etc) are not suggested even though > all these items are stored as strings. Is this a limitation? If so, is > there a way around it? > > Thanks, > Mahesh > > -- > 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:** ![Mahesh\_Kommareddi](https://avatars.discourse-cdn.com/v4/letter/m/bcef8e/32.png) [@Mahesh\_Kommareddi](https://discuss.elastic.co/u/Mahesh_Kommareddi)\ **Post date:** [November 22, 2013, 5:45pm UTC](https://discuss.elastic.co/t/completion-suggestions-with-strings-containing-only-numbers-and-strings-prefixed-with-numbers-e-g-addresses-not-working/14523/3 "2013-11-22T17:45:38Z")
Thanks a million!! As you mentioned (for the benefit of others): The standard analyzer " is built using the Standard Tokenizer[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-standard-tokenizer.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-standard-tokenizer.html)with the Standard Token Filter[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-standard-tokenfilter.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-standard-tokenfilter.html), Lower Case Token Filter[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-lowercase-tokenfilter.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-lowercase-tokenfilter.html), and Stop Token Filter[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-stop-tokenfilter.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-stop-tokenfilter.html) ." The simple analyzer "is built using a Lower Case Tokenizer[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-lowercase-tokenizer.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-lowercase-tokenizer.html)." Looking up the Lower Case Tokenizer in the docs says: "It divides text at non-letters and converts them to lower case. " Tokenizer Docs > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Standard Analyzer Doc > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Simple Analyzer Doc > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Lower Case Tokenizer Doc > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. The updated mapping using a standard analyzer is here: > I really appreciate it. Mahesh On Friday, November 22, 2013 3:24:39 AM UTC-5, Alexander Reelsen wrote: > Hey, > > try running the analyze API for numbers using the simple analyzer and > compare it with the output of the standard analyzer > > » curl 'localhost:9200/\_analyze?analyzer=standard' -d '12345' > > {"tokens":[{"token":"12345","start\_offset":0,"end\_offset":5,"type":"","position":1}]} > » curl 'localhost:9200/\_analyze?analyzer=simple' -d '12345' > {"tokens":} > > as you can see, the simple analyzer actually removed the numbers. > > So most likely the simple analyzer is not useful to return numbers in your > case and you should stick with another analyzer, as the simple analyzer > removes any numbers - which explains you not getting any results. > > --Alex > > On Thu, Nov 21, 2013 at 8:07 PM, Mahesh Kommareddi \<[mahesh.k...@gmail.com](mailto:mahesh.k...@gmail.com)\ > > > wrote: > > > Hi, > > I'm using and testing against 0.90.5 (three nodes and five shards) and > > 0.90.7 (one node and five shards). I'm interested in the completion > > suggester and it works great for items where letters are involved. For > > example, first names, last names, states, cities, or product names all > > return suggestions. This is with the help of the documentation that is on > > the Elasticsearch website: > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-suggesters-completion.html)[http://www.google.com/url?q=http%3A%2F%2Fwww.elasticsearch.org%2Fguide%2Fen%2Felasticsearch%2Freference%2Fcurrent%2Fsearch-suggesters-completion.html&sa=D&sntz=1&usg=AFQjCNFDmSngwsefS5p-Kj8yUre86kLvDw](http://www.google.com/url?q=http%3A%2F%2Fwww.elasticsearch.org%2Fguide%2Fen%2Felasticsearch%2Freference%2Fcurrent%2Fsearch-suggesters-completion.html&sa=D&sntz=1&usg=AFQjCNFDmSngwsefS5p-Kj8yUre86kLvDw) > > > > As an example, I created a 'numbers' index with a type named 'zipcode'. > > The stored document contains a field that is a string: > > [Creation of a mapping for zipcodes · GitHub](https://gist.github.com/mkommar/7586804)[https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fmkommar%2F7586804&sa=D&sntz=1&usg=AFQjCNG68i6AAACvAEeHVa\_XB5SGA0PVTQ](https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fmkommar%2F7586804&sa=D&sntz=1&usg=AFQjCNG68i6AAACvAEeHVa_XB5SGA0PVTQ) > > > > I receive: {"ok":true,"acknowledged":true} > > > > Next, I insert some zipcodes as strings: > > [Adding document to the type · GitHub](https://gist.github.com/mkommar/7586857)[https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fmkommar%2F7586857&sa=D&sntz=1&usg=AFQjCNG9CYS\_hXUQgmxfEIw\_SObAxXr84A](https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fmkommar%2F7586857&sa=D&sntz=1&usg=AFQjCNG9CYS_hXUQgmxfEIw_SObAxXr84A) > > > > I receive: > > {"ok":true,"\_index":"numbers","\_type":"zipcode","\_id":"1","\_version":1} > > {"ok":true,"\_index":"numbers","\_type":"zipcode","\_id":"2","\_version":1} > > > > Now the suggestion: > > [Asking for a suggestion based on one of the inputted documents. · GitHub](https://gist.github.com/mkommar/7587131)[https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fmkommar%2F7587131&sa=D&sntz=1&usg=AFQjCNGtgvq8MMDLSrjo4ZOye7y0MVLkqA](https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fmkommar%2F7587131&sa=D&sntz=1&usg=AFQjCNGtgvq8MMDLSrjo4ZOye7y0MVLkqA) > > > > I expect the "90210" string to be returned. However, I get no result: > > { > > "\_shards" : { > > "total" : 5, > > "successful" : 5, > > "failed" : 0 > > }, > > "numbers-suggest" : [ { > > "text" : "902", > > "offset" : 0, > > "length" : 3, > > "options" : > > } ] > > } > > > > Just to be sure, I insert an item that contains alphabetical items only > > and query for a suggestion: > > [Adding a non-numeric item and asking for a suggestion · GitHub](https://gist.github.com/mkommar/7587188)[https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fmkommar%2F7587188&sa=D&sntz=1&usg=AFQjCNGBhUvjacfd1rlwgYNRN3C8fsqIlQ](https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fmkommar%2F7587188&sa=D&sntz=1&usg=AFQjCNGBhUvjacfd1rlwgYNRN3C8fsqIlQ) > > > > Which returns a result as expected: > > { > > "\_shards" : { > > "total" : 5, > > "successful" : 5, > > "failed" : 0 > > }, > > "numbers-suggest" : [ { > > "text" : "bl", > > "offset" : 0, > > "length" : 2, > > "options" : [ { > > "text" : "Blah blah", > > "score" : 1.0, "payload" : {"area code":0} > > } ] > > } ] > > } > > > > It appears that zipcodes ("90210", "29268", "28262"), phone numbers (" > > 7042315555", "5555555555", 9999999999"), and addresses starting with > > numbers ("123 Rose Ln", "111 White St", etc) are not suggested even though > > all these items are stored as strings. Is this a limitation? If so, is > > there a way around it? > > > > Thanks, > > Mahesh > > > > -- > > 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:** ![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:05am UTC](https://discuss.elastic.co/t/completion-suggestions-with-strings-containing-only-numbers-and-strings-prefixed-with-numbers-e-g-addresses-not-working/14523/4 "2017-07-06T02:05:19Z")