# Filter facet values on another field **URL:** \ **Category:** Elasticsearch\ **Created:** [June 13, 2013, 7:05pm UTC](https://discuss.elastic.co/t/filter-facet-values-on-another-field/12403 "2013-06-13T19:05:20Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Ron](https://avatars.discourse-cdn.com/v4/letter/r/ecae2f/32.png) [@Ron](https://discuss.elastic.co/u/Ron)\ **Post date:** [June 13, 2013, 7:05pm UTC](https://discuss.elastic.co/t/filter-facet-values-on-another-field/12403/1 "2013-06-13T19:05:20Z")
Hi, We store in arrays values with related flags. The following example stores if a book is available in a specific format (we need this format for the none ElasticSearch-part of our application): { "formats" : [ { "name" : "paperback" , "available" : true }, { "name" : "hardcover" , "available" : false } ] } We want to create facets for "available formats" (would contain "paperback") and "unavailable formats" (would contain "hardcover"), i.e. if a "name" is included as a facet value depends on the field "available". What's the best way to achieve this with ElasticSearch? Can we create a mapping which tells the indexer to add only "name" values into a field "available\_formats" if the related "available" value is true? Or would we have to do this separation already before the data is send to ElasticSearch? Many thanks! Ron -- 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:** ![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:** [June 14, 2013, 4:00pm UTC](https://discuss.elastic.co/t/filter-facet-values-on-another-field/12403/2 "2013-06-14T16:00:57Z")
Can you illustrate a little what kind of output you are expecting? I'm wondering if you could use here 4 filter\_facet, one for each combination of name/availabilty. But you need to use nested documents prior to this. -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 13 juin 2013 à 21:05, Ron [elasticsearch@collaborne.com](mailto:elasticsearch@collaborne.com) a écrit : > Hi, > > We store in arrays values with related flags. The following example stores if a book is available in a specific format (we need this format for the none Elasticsearch-part of our application): > > { > "formats" : [ > { "name" : "paperback" , "available" : true }, > { "name" : "hardcover" , "available" : false } > ] > } > > We want to create facets for "available formats" (would contain "paperback") and "unavailable formats" (would contain "hardcover"), i.e. if a "name" is included as a facet value depends on the field "available". > > What's the best way to achieve this with Elasticsearch? Can we create a mapping which tells the indexer to add only "name" values into a field "available\_formats" if the related "available" value is true? Or would we have to do this separation already before the data is send to Elasticsearch? > > Many thanks! > > Ron > > -- > 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:** ![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:** [June 14, 2013, 7:51pm UTC](https://discuss.elastic.co/t/filter-facet-values-on-another-field/12403/3 "2013-06-14T19:51:50Z")
Can you illustrate a little what kind of output you are expecting? I'm wondering if you could use here 4 filter\_facet, one for each combination of name/availabilty. But you need to use nested documents prior to this. -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 13 juin 2013 à 21:05, Ron [elasticsearch@collaborne.com](mailto:elasticsearch@collaborne.com) a écrit : > Hi, > > We store in arrays values with related flags. The following example stores if a book is available in a specific format (we need this format for the none Elasticsearch-part of our application): > > { > "formats" : [ > { "name" : "paperback" , "available" : true }, > { "name" : "hardcover" , "available" : false } > ] > } > > We want to create facets for "available formats" (would contain "paperback") and "unavailable formats" (would contain "hardcover"), i.e. if a "name" is included as a facet value depends on the field "available". > > What's the best way to achieve this with Elasticsearch? Can we create a mapping which tells the indexer to add only "name" values into a field "available\_formats" if the related "available" value is true? Or would we have to do this separation already before the data is send to Elasticsearch? > > Many thanks! > > Ron > > -- > 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:** ![Ron](https://avatars.discourse-cdn.com/v4/letter/r/ecae2f/32.png) [@Ron](https://discuss.elastic.co/u/Ron)\ **Post date:** [June 18, 2013, 2:55pm UTC](https://discuss.elastic.co/t/filter-facet-values-on-another-field/12403/4 "2013-06-18T14:55:48Z")
Hi David, Many thanks for your response! The output should look like two normal facets: "facets" : { "available\_formats" : { ... "terms" : [ { "term" : "paperback", "count" : 10 }, { "term" : "hardcover", "count" : 7 }, { "term" : "audio", "count" : 3 } ] }, "unavailable\_formats" : { ... "terms" : [ { "term" : "paperback", "count" : 4 }, { "term" : "hardcover", "count" : 8 }, { "term" : "audio", "count" : 1 } ] } } The Paperback/hardcover field is just an example. We have other examples where there is a flag (like 'available') but 100s of values (like 'paperback/hardcover'). Ron On Friday, June 14, 2013 6:00:57 PM UTC+2, David Pilato wrote: > Can you illustrate a little what kind of output you are expecting? > I'm wondering if you could use here 4 filter\_facet, one for each > combination of name/availabilty. > > But you need to use nested documents prior to this. > > -- > _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) > | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > Le 13 juin 2013 à 21:05, Ron \<[elasti...@collaborne.com](mailto:elasti...@collaborne.com) \\> a > écrit : > > Hi, > > We store in arrays values with related flags. The following example stores > if a book is available in a specific format (we need this format for the > none Elasticsearch-part of our application): > > { > "formats" : [ > { "name" : "paperback" , "available" : true }, > { "name" : "hardcover" , "available" : false } > ] > } > > We want to create facets for "available formats" (would contain > "paperback") and "unavailable formats" (would contain "hardcover"), i.e. if > a "name" is included as a facet value depends on the field "available". > > What's the best way to achieve this with Elasticsearch? Can we create a > mapping which tells the indexer to add only "name" values into a field > "available\_formats" if the related "available" value is true? Or would we > have to do this separation already before the data is send to Elasticsearch? > > Many thanks! > > Ron > > -- > 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:** ![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:** [June 18, 2013, 3:31pm UTC](https://discuss.elastic.co/t/filter-facet-values-on-another-field/12403/5 "2013-06-18T15:31:56Z")
Why not indexing your documents in another way? { "formats" : { "available" : ["paperback"], "unavailable" : ["hardcover"] } } Does it help? -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 18 juin 2013 à 16:55, Ron [elasticsearch@collaborne.com](mailto:elasticsearch@collaborne.com) a écrit : > Hi David, > > Many thanks for your response! > > The output should look like two normal facets: > "facets" : { > "available\_formats" : { > ... > "terms" : [ { > "term" : "paperback", > "count" : 10 > }, > { > "term" : "hardcover", > "count" : 7 > }, > { > "term" : "audio", > "count" : 3 > } ] > }, > "unavailable\_formats" : { > ... > "terms" : [ { > "term" : "paperback", > "count" : 4 > }, > { > "term" : "hardcover", > "count" : 8 > }, > { > "term" : "audio", > "count" : 1 > } ] > } > } > > The Paperback/hardcover field is just an example. We have other examples where there is a flag (like 'available') but 100s of values (like 'paperback/hardcover'). > > Ron > > On Friday, June 14, 2013 6:00:57 PM UTC+2, David Pilato wrote: > Can you illustrate a little what kind of output you are expecting? > I'm wondering if you could use here 4 filter\_facet, one for each combination of name/availabilty. > > But you need to use nested documents prior to this. > > -- > David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) > @dadoonet | @elasticsearchfr | @scrutmydocs > > Le 13 juin 2013 à 21:05, Ron [elasti...@collaborne.com](mailto:elasti...@collaborne.com) a écrit : > > > Hi, > > > > We store in arrays values with related flags. The following example stores if a book is available in a specific format (we need this format for the none Elasticsearch-part of our application): > > > > { > > "formats" : [ > > { "name" : "paperback" , "available" : true }, > > { "name" : "hardcover" , "available" : false } > > ] > > } > > > > We want to create facets for "available formats" (would contain "paperback") and "unavailable formats" (would contain "hardcover"), i.e. if a "name" is included as a facet value depends on the field "available". > > > > What's the best way to achieve this with Elasticsearch? Can we create a mapping which tells the indexer to add only "name" values into a field "available\_formats" if the related "available" value is true? Or would we have to do this separation already before the data is send to Elasticsearch? > > > > Many thanks! > > > > Ron > > > > -- > > 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:** ![Ron](https://avatars.discourse-cdn.com/v4/letter/r/ecae2f/32.png) [@Ron](https://discuss.elastic.co/u/Ron)\ **Post date:** [June 18, 2013, 4:14pm UTC](https://discuss.elastic.co/t/filter-facet-values-on-another-field/12403/6 "2013-06-18T16:14:41Z")
Pre-processing the input data is indeed what we ended up with. It's just not so nice because it requires us to store the data in both formats (the original one which we need for the rest of our application and the one for Elasticsearch) in MongoDB, from where it's pushed via the MongoDB river. It would had been cool if we could have defined this filtering just on the Elasticsearch indexing level. Anyway, now we implemented the pre-processing logic and push the data in the proposed format into Elasticsearch. Ron On Tuesday, June 18, 2013 5:31:56 PM UTC+2, David Pilato wrote: > Why not indexing your documents in another way? > { > "formats" : { > "available" : ["paperback"], > "unavailable" : ["hardcover"] > } > } > > Does it help? > > -- > _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) > | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > Le 18 juin 2013 à 16:55, Ron \<[elasti...@collaborne.com](mailto:elasti...@collaborne.com) \\> a > écrit : > > Hi David, > > Many thanks for your response! > > The output should look like two normal facets: > "facets" : { > "available\_formats" : { > ... > "terms" : [ { > "term" : "paperback", > "count" : 10 > }, > { > "term" : "hardcover", > "count" : 7 > }, > { > "term" : "audio", > "count" : 3 > } ] > }, > "unavailable\_formats" : { > ... > "terms" : [ { > "term" : "paperback", > "count" : 4 > }, > { > "term" : "hardcover", > "count" : 8 > }, > { > "term" : "audio", > "count" : 1 > } ] > } > } > > The Paperback/hardcover field is just an example. We have other examples > where there is a flag (like 'available') but 100s of values (like > 'paperback/hardcover'). > > Ron > > On Friday, June 14, 2013 6:00:57 PM UTC+2, David Pilato wrote: > > > Can you illustrate a little what kind of output you are expecting? > > I'm wondering if you could use here 4 filter\_facet, one for each > > combination of name/availabilty. > > > > But you need to use nested documents prior to this. > > > > -- > > _David Pilato_ | _Technical Advocate_ | \*[Elasticsearch.com](http://Elasticsearch.com)[http://elasticsearch.com/](http://elasticsearch.com/) > > \* > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > Le 13 juin 2013 à 21:05, Ron [elasti...@collaborne.com](mailto:elasti...@collaborne.com) a écrit : > > > > Hi, > > > > We store in arrays values with related flags. The following example > > stores if a book is available in a specific format (we need this format for > > the none Elasticsearch-part of our application): > > > > { > > "formats" : [ > > { "name" : "paperback" , "available" : true }, > > { "name" : "hardcover" , "available" : false } > > ] > > } > > > > We want to create facets for "available formats" (would contain > > "paperback") and "unavailable formats" (would contain "hardcover"), i.e. if > > a "name" is included as a facet value depends on the field "available". > > > > What's the best way to achieve this with Elasticsearch? Can we create a > > mapping which tells the indexer to add only "name" values into a field > > "available\_formats" if the related "available" value is true? Or would we > > have to do this separation already before the data is send to Elasticsearch? > > > > Many thanks! > > > > Ron > > > > -- > > 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 [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:** ![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:** [June 19, 2013, 8:38am UTC](https://discuss.elastic.co/t/filter-facet-values-on-another-field/12403/7 "2013-06-19T08:38:13Z")
## May be you can use a ScriptFilter in MongoDB river to handle it: [Home · richardwilly98/elasticsearch-river-mongodb Wiki · GitHub](https://github.com/richardwilly98/elasticsearch-river-mongodb/wiki#script-filters) David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 18 juin 2013 à 18:14, Ron [elasticsearch@collaborne.com](mailto:elasticsearch@collaborne.com) a écrit : > Pre-processing the input data is indeed what we ended up with. It's just not so nice because it requires us to store the data in both formats (the original one which we need for the rest of our application and the one for Elasticsearch) in MongoDB, from where it's pushed via the MongoDB river. > > It would had been cool if we could have defined this filtering just on the Elasticsearch indexing level. Anyway, now we implemented the pre-processing logic and push the data in the proposed format into Elasticsearch. > > Ron > > On Tuesday, June 18, 2013 5:31:56 PM UTC+2, David Pilato wrote: > Why not indexing your documents in another way? > { > "formats" : { > "available" : ["paperback"], > "unavailable" : ["hardcover"] > } > } > > Does it help? > > -- > David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) > @dadoonet | @elasticsearchfr | @scrutmydocs > > Le 18 juin 2013 à 16:55, Ron [elasti...@collaborne.com](mailto:elasti...@collaborne.com) a écrit : > > > Hi David, > > > > Many thanks for your response! > > > > The output should look like two normal facets: > > "facets" : { > > "available\_formats" : { > > ... > > "terms" : [ { > > "term" : "paperback", > > "count" : 10 > > }, > > { > > "term" : "hardcover", > > "count" : 7 > > }, > > { > > "term" : "audio", > > "count" : 3 > > } ] > > }, > > "unavailable\_formats" : { > > ... > > "terms" : [ { > > "term" : "paperback", > > "count" : 4 > > }, > > { > > "term" : "hardcover", > > "count" : 8 > > }, > > { > > "term" : "audio", > > "count" : 1 > > } ] > > } > > } > > > > The Paperback/hardcover field is just an example. We have other examples where there is a flag (like 'available') but 100s of values (like 'paperback/hardcover'). > > > > Ron > > > > On Friday, June 14, 2013 6:00:57 PM UTC+2, David Pilato wrote: > > Can you illustrate a little what kind of output you are expecting? > > I'm wondering if you could use here 4 filter\_facet, one for each combination of name/availabilty. > > > > But you need to use nested documents prior to this. > > > > -- > > David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) > > @dadoonet | @elasticsearchfr | @scrutmydocs > > > > Le 13 juin 2013 à 21:05, Ron [elasti...@collaborne.com](mailto:elasti...@collaborne.com) a écrit : > > > > > Hi, > > > > > > We store in arrays values with related flags. The following example stores if a book is available in a specific format (we need this format for the none Elasticsearch-part of our application): > > > > > > { > > > "formats" : [ > > > { "name" : "paperback" , "available" : true }, > > > { "name" : "hardcover" , "available" : false } > > > ] > > > } > > > > > > We want to create facets for "available formats" (would contain "paperback") and "unavailable formats" (would contain "hardcover"), i.e. if a "name" is included as a facet value depends on the field "available". > > > > > > What's the best way to achieve this with Elasticsearch? Can we create a mapping which tells the indexer to add only "name" values into a field "available\_formats" if the related "available" value is true? Or would we have to do this separation already before the data is send to Elasticsearch? > > > > > > Many thanks! > > > > > > Ron > > > > > > -- > > > 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 [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:30am UTC](https://discuss.elastic.co/t/filter-facet-values-on-another-field/12403/8 "2017-07-06T02:30:25Z")