# Not able to search long values **URL:** \ **Category:** Elasticsearch\ **Created:** [October 15, 2014, 5:23am UTC](https://discuss.elastic.co/t/not-able-to-search-long-values/20257 "2014-10-15T05:23:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Reeni\_Mathew](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@Reeni\_Mathew](https://discuss.elastic.co/u/Reeni_Mathew)\ **Post date:** [October 15, 2014, 5:23am UTC](https://discuss.elastic.co/t/not-able-to-search-long-values/20257/1 "2014-10-15T05:23:27Z")
Hi Team, I have an index with the below mapping. { "merchant\_customer":{ "properties":{ "ADDRESS1":{"type":"string"}, "ADDRESS2":{"type":"string"}, "CITY\_NAME":{"type":"string"}, "COUNTRY\_CODE":{"type":"string"}, "CUSTOMER\_NUMBER":{"type":"long"}, "MERCHANT\_NUMBER":{"type":"long"}, "POSTAL\_CODE":{"type":"string"}, "SHIPPING\_POSTAL\_ADDRESS\_ID":{"type":"long"} } } } And I tried searching the CUSTOMER\_NUMBER and MERCHANT\_NUMBER from Head plugin as well as from Kibana UI. But its not getting searched. I even tried to explicitly provide \*"index":"not\_analyzed" \*for CUSTOMER\_NUMBER and MERCHANT\_NUMBER. Even that didn't work. Only after changing these fields to String, I was able to search on these fields. [Eg: CUSTOMER\_NUMBER 1234567899876543210] Can someone tell me why is the behaviour like this? Thanks Reeni -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d0078d5b-b443-4030-beba-150fa5cbf7c8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d0078d5b-b443-4030-beba-150fa5cbf7c8%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![PatriaCoutee](https://avatars.discourse-cdn.com/v4/letter/p/4da419/32.png) [@PatriaCoutee](https://discuss.elastic.co/u/PatriaCoutee)\ **Post date:** [October 15, 2014, 9:09am UTC](https://discuss.elastic.co/t/not-able-to-search-long-values/20257/2 "2014-10-15T09:09:27Z")
The activity of the animal beings has become acutely active everywhere on this earth. Bodies do not get time to booty a blow for a while. With the accretion use of altered gadgets of Gps Jammer, the possibilities of accepting the aboriginal of blow accept absolutely finished. The adaptable phones or the corpuscle phones are some of these accessories that accumulate the bodies consistently in blow with the alfresco world. The adaptable building are additionally accessible about everywhere these canicule and due to this the accessibility of the Cell Phone Jammer has become alike added quick and authentic. Today, you cannot break out of ability of these adaptable building as their signals can bolt your about anywhere. The bearings of bodies who accord to altered business professions has become actual analytical of **[Audio Signal Jammer](http://www.jammerinthebox.com/categories/Wireless_Video%7B47%7DAudio_Signal_Jammer/)** as their authorities bolt them anywhere any moment. ---
**Author:** ![Dan\_Fairs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_fairs/32/1205_2.png) [@Dan\_Fairs](https://discuss.elastic.co/u/Dan_Fairs)\ **Post date:** [October 15, 2014, 4:02pm UTC](https://discuss.elastic.co/t/not-able-to-search-long-values/20257/3 "2014-10-15T16:02:55Z")
Hi > And I tried searching the CUSTOMER\_NUMBER and MERCHANT\_NUMBER from Head > plugin as well as from Kibana UI. > But its not getting searched. I even tried to explicitly provide \*"index":"not\_analyzed" > \*for CUSTOMER\_NUMBER and MERCHANT\_NUMBER. > Even that didn't work. Only after changing these fields to String, I was > able to search on these fields. [Eg: CUSTOMER\_NUMBER 1234567899876543210] > Can someone tell me why is the behaviour like this? It's probably Kibana. Javascript has problems with very large numbers - we encountered a similar problem recently while messing around with head. Try running your query directly with curl, or something else that doesn't have javascript in the pipeline. (Interesting aside: we also noticed that the popular 'jq' utility also has problems with long values...) Cheers, Dan -- Dan Fairs [dan.fairs@gmail.com](mailto:dan.fairs@gmail.com) | @danfairs -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAJn\_wTHham95PQ1JdEZiqE388cXOqcFQEVxdVCJnU6%3D54mMCwA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAJn_wTHham95PQ1JdEZiqE388cXOqcFQEVxdVCJnU6%3D54mMCwA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:56am UTC](https://discuss.elastic.co/t/not-able-to-search-long-values/20257/4 "2017-07-06T00:56:00Z")