# Include special Symbol **URL:** \ **Category:** Elasticsearch\ **Created:** [February 26, 2014, 3:00pm UTC](https://discuss.elastic.co/t/include-special-symbol/16035 "2014-02-26T15:00:24Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Nick\_Chang\_2](https://avatars.discourse-cdn.com/v4/letter/n/7c8e57/32.png) [@Nick\_Chang\_2](https://discuss.elastic.co/u/Nick_Chang_2)\ **Post date:** [February 26, 2014, 3:00pm UTC](https://discuss.elastic.co/t/include-special-symbol/16035/1 "2014-02-26T15:00:24Z")
Hello I have column include special symbol. Ex: user : (Google)abc@gmail.com I want to count. POST /datas/\_search { "facets": { "terms": { "terms": { "field": "user", "size": 10 } } } } But, result is not right. "term": "[gmail.com](http://gmail.com)", "count": 564987 }, { "term": "facebook", "count": 475632 }, { "term": "google", "count": 411384 Can I to solve this problem?? Thanks -- 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/532e8f3c-a643-452d-934c-b71774201f18%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/532e8f3c-a643-452d-934c-b71774201f18%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Binh\_Ly\_2](https://avatars.discourse-cdn.com/v4/letter/b/d07c76/32.png) [@Binh\_Ly\_2](https://discuss.elastic.co/u/Binh_Ly_2)\ **Post date:** [February 26, 2014, 3:03pm UTC](https://discuss.elastic.co/t/include-special-symbol/16035/2 "2014-02-26T15:03:29Z")
You'll likely need that field to be unanalyzed (i.e. tell ES not to cut it up in the index). One way is to predefine that field in your mapping as: "user": { "type": "string", "index": "not\_analyzed" } More details here: [http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html) -- 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/805a1632-7e84-416f-8d7a-d5b9f327b8aa%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/805a1632-7e84-416f-8d7a-d5b9f327b8aa%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Nick\_Chang\_2](https://avatars.discourse-cdn.com/v4/letter/n/7c8e57/32.png) [@Nick\_Chang\_2](https://discuss.elastic.co/u/Nick_Chang_2)\ **Post date:** [February 26, 2014, 3:22pm UTC](https://discuss.elastic.co/t/include-special-symbol/16035/3 "2014-02-26T15:22:50Z")
Hello Binh I used elasticsearch-river-mongo plugin. How to modify this index?? Thanks for your reply Binh Ly於 2014年2月26日星期三UTC+8下午11時03分29秒寫道： > You'll likely need that field to be unanalyzed (i.e. tell ES not to cut it > up in the index). One way is to predefine that field in your mapping as: > > "user": { > "type": "string", > "index": "not\_analyzed" > } > > More details here: > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html) -- 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/96a3b201-adef-4fc8-95da-96633ffa6112%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/96a3b201-adef-4fc8-95da-96633ffa6112%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Nick\_Chang\_2](https://avatars.discourse-cdn.com/v4/letter/n/7c8e57/32.png) [@Nick\_Chang\_2](https://discuss.elastic.co/u/Nick_Chang_2)\ **Post date:** [February 27, 2014, 6:05am UTC](https://discuss.elastic.co/t/include-special-symbol/16035/4 "2014-02-27T06:05:52Z")
Hello I already solve this problem. Your suggest is right. Thanks Nick Binh Ly於 2014年2月26日星期三UTC+8下午11時03分29秒寫道： > You'll likely need that field to be unanalyzed (i.e. tell ES not to cut it > up in the index). One way is to predefine that field in your mapping as: > > "user": { > "type": "string", > "index": "not\_analyzed" > } > > More details here: > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html) -- 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/c7005059-e547-460e-a37c-fa1f6a020947%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c7005059-e547-460e-a37c-fa1f6a020947%40googlegroups.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, 1:46am UTC](https://discuss.elastic.co/t/include-special-symbol/16035/5 "2017-07-06T01:46:57Z")
Closed on July 6, 2017, 1:46am UTC