# Elasticsearch 1.0 RC 1 - strange issue with multi\_fields faceting **URL:** \ **Category:** Elasticsearch\ **Created:** [February 6, 2014, 11:05am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-rc-1-strange-issue-with-multi-fields-faceting/15639 "2014-02-06T11:05:20Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Guillermo\_Arias\_del\_](https://avatars.discourse-cdn.com/v4/letter/g/cab0a1/32.png) [@Guillermo\_Arias\_del\_](https://discuss.elastic.co/u/Guillermo_Arias_del_)\ **Post date:** [February 6, 2014, 11:05am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-rc-1-strange-issue-with-multi-fields-faceting/15639/1 "2014-02-06T11:05:20Z")
Hi, all! I am using multi fields in my application in order to be able to search using different index analyzers and perform faceting on the "untouched" version of the field. The untouched version is always called like the field itself and marked as "not\_analyzed". This enables me to use the name directly on the facets. On the other hand, I have an "index\_analyzer" for my whole type. This wasn't a problem with ES 0.90, but it is with 1.0rc1. A Gist is worth a thousand words: > Just removing the "index\_analyzer" makes it work. Do I miss something? I thought that this "index\_analyzer" is only used when no one is specified for an analyzed field, but the field is "not\_analyzed". Cheers, Guillermo. -- 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/4e50b688-1a48-444c-8925-f4015a35129d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4e50b688-1a48-444c-8925-f4015a35129d%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [February 6, 2014, 11:07am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-rc-1-strange-issue-with-multi-fields-faceting/15639/2 "2014-02-06T11:07:37Z")
Not tested but I think you should do something like: [https://gist.github.com/dadoonet/8842209](https://gist.github.com/dadoonet/8842209) HTH -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 6 février 2014 at 12:05:25, Guillermo Arias del Río ([ariasdelrio@gmail.com](mailto:ariasdelrio@gmail.com)) a écrit: Hi, all! I am using multi fields in my application in order to be able to search using different index analyzers and perform faceting on the "untouched" version of the field. The untouched version is always called like the field itself and marked as "not\_analyzed". This enables me to use the name directly on the facets. On the other hand, I have an "index\_analyzer" for my whole type. This wasn't a problem with ES 0.90, but it is with 1.0rc1. A Gist is worth a thousand words: > Just removing the "index\_analyzer" makes it work. Do I miss something? I thought that this "index\_analyzer" is only used when no one is specified for an analyzed field, but the field is "not\_analyzed". Cheers, ## Guillermo. 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/4e50b688-1a48-444c-8925-f4015a35129d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4e50b688-1a48-444c-8925-f4015a35129d%40googlegroups.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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/etPan.52f36cf9.2f305def.d955%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.52f36cf9.2f305def.d955%40MacBook-Air-de-David.local). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Guillermo\_Arias\_del\_](https://avatars.discourse-cdn.com/v4/letter/g/cab0a1/32.png) [@Guillermo\_Arias\_del\_](https://discuss.elastic.co/u/Guillermo_Arias_del_)\ **Post date:** [February 6, 2014, 11:14am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-rc-1-strange-issue-with-multi-fields-faceting/15639/3 "2014-02-06T11:14:53Z")
Sorry, I forgot to write the responses: With "index\_analyzer" set: { ... "facets": { "myfacet": { "\_type": "terms", "missing": 0, "other": 98, "terms": [ { "count": 3, "term": "e" }, { "count": 1, "term": "eo" }, { "count": 1, "term": "eon" }, ... Without "index\_analyzer": "facets": { "myfacet": { "\_type": "terms", "missing": 0, "other": 0, "terms": [ { "count": 1, "term": "someone" }, { "count": 2, "term": "something" } ], ... -- 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/2a7f9cc2-a22b-40ef-b860-8414208dd745%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2a7f9cc2-a22b-40ef-b860-8414208dd745%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Guillermo\_Arias\_del\_](https://avatars.discourse-cdn.com/v4/letter/g/cab0a1/32.png) [@Guillermo\_Arias\_del\_](https://discuss.elastic.co/u/Guillermo_Arias_del_)\ **Post date:** [February 6, 2014, 11:34am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-rc-1-strange-issue-with-multi-fields-faceting/15639/4 "2014-02-06T11:34:50Z")
Hi, David, Thanks for the tip about not having to repeat the field name... reading here[http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/\_multi\_fields.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/_multi_fields.html), I didn't notice that difference 🙂 It works now. El jueves, 6 de febrero de 2014 12:07:37 UTC+1, David Pilato escribió: > Not tested but I think you should do something like: > [gist:8842209 · GitHub](https://gist.github.com/dadoonet/8842209) > > HTH > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > Le 6 février 2014 at 12:05:25, Guillermo Arias del Río ([arias...@gmail.com](mailto:arias...@gmail.com)\) > a écrit: > > Hi, all! > > I am using multi fields in my application in order to be able to search > using different index analyzers and perform faceting on the "untouched" > version of the field. The untouched version is always called like the field > itself and marked as "not\_analyzed". This enables me to use the name > directly on the facets. On the other hand, I have an "index\_analyzer" for > my whole type. This wasn't a problem with ES 0.90, but it is with 1.0rc1. > > A Gist is worth a thousand words: > > [multi\_field and faceting in ES 1.0rc1 · GitHub](https://gist.github.com/ariasdelrio/8842138) > > Just removing the "index\_analyzer" makes it work. > > Do I miss something? I thought that this "index\_analyzer" is only used > when no one is specified for an analyzed field, but the field is > "not\_analyzed". > > Cheers, > > ## Guillermo. > > 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) \. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/4e50b688-1a48-444c-8925-f4015a35129d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4e50b688-1a48-444c-8925-f4015a35129d%40googlegroups.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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/a71c3a0f-2438-46bc-bd5e-ff2b9e60461a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a71c3a0f-2438-46bc-bd5e-ff2b9e60461a%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:52am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-rc-1-strange-issue-with-multi-fields-faceting/15639/5 "2017-07-06T01:52:02Z")