# Analyzers and faceting and unknown data **URL:** \ **Category:** Elasticsearch\ **Created:** [February 3, 2013, 4:57am UTC](https://discuss.elastic.co/t/analyzers-and-faceting-and-unknown-data/10606 "2013-02-03T04:57:59Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![nullpainter](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nullpainter/32/2504_2.png) [@nullpainter](https://discuss.elastic.co/u/nullpainter)\ **Post date:** [February 3, 2013, 4:57am UTC](https://discuss.elastic.co/t/analyzers-and-faceting-and-unknown-data/10606/1 "2013-02-03T04:57:59Z")
I am developing a system that as well as a core, predefined schema being indexed by elasticsearch, also contains arbitrary user-supplied JSON. I am using the snowball analyser for all data. I am wishing to provide the ability for users to perform a faceted search over any of their arbitrary fields. However because the fields are being indexed using snowball, the terms being retrieved for faceting are incorrect (singular rather than plural in some cases - which is fine - but completely bogus prefixes in others). I was hoping that adding a "\_all" : { "store": "yes" } would do the trick, but no such luck. Is there an easy solution? Or do I need to index each field twice, one wit the snowball analyser (for searching) and one with no analysers (for faceting)? M -- 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:** [February 3, 2013, 7:13am UTC](https://discuss.elastic.co/t/analyzers-and-faceting-and-unknown-data/10606/2 "2013-02-03T07:13:45Z")
I usualy use multifield feature for that. field.field is analyzed field.facet is not analyzed IMHO, using \_all in facets is risky. You could hit some Out Of Memory Exception issues. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 3 févr. 2013 à 05:57, Matt Painter [matt@deity.co.nz](mailto:matt@deity.co.nz) a écrit : I am developing a system that as well as a core, predefined schema being indexed by elasticsearch, also contains arbitrary user-supplied JSON. I am using the snowball analyser for all data. I am wishing to provide the ability for users to perform a faceted search over any of their arbitrary fields. However because the fields are being indexed using snowball, the terms being retrieved for faceting are incorrect (singular rather than plural in some cases - which is fine - but completely bogus prefixes in others). I was hoping that adding a "\_all" : { "store": "yes" } would do the trick, but no such luck. Is there an easy solution? Or do I need to index each field twice, one wit the snowball analyser (for searching) and one with no analysers (for faceting)? ## M 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:** ![nullpainter](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nullpainter/32/2504_2.png) [@nullpainter](https://discuss.elastic.co/u/nullpainter)\ **Post date:** [February 3, 2013, 8:00am UTC](https://discuss.elastic.co/t/analyzers-and-faceting-and-unknown-data/10606/3 "2013-02-03T08:00:59Z")
Thanks for that David - didn't realise that existed. Looks like some fun JSON munging for me! M PS. Thanks for the word of warning re: \_all - noted. On Sunday, February 3, 2013 8:13:45 PM UTC+13, David Pilato wrote: > I usualy use multifield feature for that. > > field.field is analyzed > field.facet is not analyzed > > IMHO, using \_all in facets is risky. You could hit some Out Of Memory > Exception issues. > > -- > David 😉 > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 3 févr. 2013 à 05:57, Matt Painter \\> a > écrit : > > I am developing a system that as well as a core, predefined schema being > indexed by elasticsearch, also contains arbitrary user-supplied JSON. I am > using the snowball analyser for all data. > > I am wishing to provide the ability for users to perform a faceted search > over any of their arbitrary fields. However because the fields are being > indexed using snowball, the terms being retrieved for faceting are > incorrect (singular rather than plural in some cases - which is fine - but > completely bogus prefixes in others). I was hoping that adding a "\_all" : > { "store": "yes" } would do the trick, but no such luck. > > Is there an easy solution? Or do I need to index each field twice, one wit > the snowball analyser (for searching) and one with no analysers (for > faceting)? > > M > > -- > 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:** ![nullpainter](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nullpainter/32/2504_2.png) [@nullpainter](https://discuss.elastic.co/u/nullpainter)\ **Post date:** [February 3, 2013, 8:19am UTC](https://discuss.elastic.co/t/analyzers-and-faceting-and-unknown-data/10606/4 "2013-02-03T08:19:12Z")
Actually, how would that technique work for faceting data which is almost entirely dynamically-mapped? I only know the fields and field structure at the point of the request for indexing being retrieved and, as far as I know, one can't index both a document and include specific mapping at the same time (maybe? I'm pretty new to Elastic). FWIW, my data structure is this: class Record { // User-supplied JSON metadata List metadata; ... other known fields; } where the top-level Record is indexed into Elasticsearch, has a bunch of known fields and a list of arbitrary raw JSON metadata - which is what we need faceting on. I realise that not having a known schema is limiting what we can get out of Elasticsearch, but I'm trying to make the barrier for users to index and search on arbitrary content as low as possible. M On 3 February 2013 21:00, Matt Painter [matt@deity.co.nz](mailto:matt@deity.co.nz) wrote: > Thanks for that David - didn't realise that existed. Looks like some fun > JSON munging for me! > > M > > PS. Thanks for the word of warning re: \_all - noted. > > On Sunday, February 3, 2013 8:13:45 PM UTC+13, David Pilato wrote: > > > I usualy use multifield feature for that. > > > > field.field is analyzed > > field.facet is not analyzed > > > > IMHO, using \_all in facets is risky. You could hit some Out Of Memory > > Exception issues. > > > > -- > > David 😉 > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > > Le 3 févr. 2013 à 05:57, Matt Painter [ma...@deity.co.nz](mailto:ma...@deity.co.nz) a écrit : > > > > I am developing a system that as well as a core, predefined schema being > > indexed by elasticsearch, also contains arbitrary user-supplied JSON. I am > > using the snowball analyser for all data. > > > > I am wishing to provide the ability for users to perform a faceted search > > over any of their arbitrary fields. However because the fields are being > > indexed using snowball, the terms being retrieved for faceting are > > incorrect (singular rather than plural in some cases - which is fine - but > > completely bogus prefixes in others). I was hoping that adding a "\_all" > > : { "store": "yes" } would do the trick, but no such luck. > > > > Is there an easy solution? Or do I need to index each field twice, one > > wit the snowball analyser (for searching) and one with no analysers (for > > faceting)? > > > > M > > > > -- > > 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](http://googlegroups.com). > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[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). -- Matt Painter matt@deity.co.nz +64 21 115 9378 -- 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:** ![nullpainter](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nullpainter/32/2504_2.png) [@nullpainter](https://discuss.elastic.co/u/nullpainter)\ **Post date:** [February 3, 2013, 8:27am UTC](https://discuss.elastic.co/t/analyzers-and-faceting-and-unknown-data/10606/5 "2013-02-03T08:27:42Z")
Aha, have just discovered the section in the doco about dynamic\_templateswith an explicit example featuring multi\_field. Looks like it may be what I'm after? On 3 February 2013 21:19, Matt Painter [matt@deity.co.nz](mailto:matt@deity.co.nz) wrote: > Actually, how would that technique work for faceting data which is almost > entirely dynamically-mapped? I only know the fields and field structure at > the point of the request for indexing being retrieved and, as far as I > know, one can't index both a document and include specific mapping at the > same time (maybe? I'm pretty new to Elastic). > > FWIW, my data structure is this: > > class Record { > > // User-supplied JSON metadata > List metadata; > > ... > > other known fields; > } > > where the top-level Record is indexed into Elasticsearch, has a bunch of > known fields and a list of arbitrary raw JSON metadata - which is what we > need faceting on. > > I realise that not having a known schema is limiting what we can get out > of Elasticsearch, but I'm trying to make the barrier for users to index and > search on arbitrary content as low as possible. > > M > > On 3 February 2013 21:00, Matt Painter [matt@deity.co.nz](mailto:matt@deity.co.nz) wrote: > > > Thanks for that David - didn't realise that existed. Looks like some fun > > JSON munging for me! > > > > M > > > > PS. Thanks for the word of warning re: \_all - noted. > > > > On Sunday, February 3, 2013 8:13:45 PM UTC+13, David Pilato wrote: > > > > > I usualy use multifield feature for that. > > > > > > field.field is analyzed > > > field.facet is not analyzed > > > > > > IMHO, using \_all in facets is risky. You could hit some Out Of Memory > > > Exception issues. > > > > > > -- > > > David 😉 > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > > > > Le 3 févr. 2013 à 05:57, Matt Painter [ma...@deity.co.nz](mailto:ma...@deity.co.nz) a écrit : > > > > > > I am developing a system that as well as a core, predefined schema being > > > indexed by elasticsearch, also contains arbitrary user-supplied JSON. I am > > > using the snowball analyser for all data. > > > > > > I am wishing to provide the ability for users to perform a faceted > > > search over any of their arbitrary fields. However because the fields are > > > being indexed using snowball, the terms being retrieved for faceting are > > > incorrect (singular rather than plural in some cases - which is fine - but > > > completely bogus prefixes in others). I was hoping that adding a "\_all" > > > : { "store": "yes" } would do the trick, but no such luck. > > > > > > Is there an easy solution? Or do I need to index each field twice, one > > > wit the snowball analyser (for searching) and one with no analysers (for > > > faceting)? > > > > > > M > > > > > > -- > > > 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](http://googlegroups.com). > > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[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). > > -- > Matt Painter > matt@deity.co.nz > +64 21 115 9378 -- Matt Painter matt@deity.co.nz +64 21 115 9378 -- 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:** [February 3, 2013, 10:18am UTC](https://discuss.elastic.co/t/analyzers-and-faceting-and-unknown-data/10606/6 "2013-02-03T10:18:33Z")
If your documents look like { "metadata":["value1", "value2"...] } You only have to define a mapping for your field metadata using multifield. If users will add new fields, like: { "metadata1":"value1", "metadata2":"value2"... } I think that dynamic\_templates will help. How does your JSON doc look like at the end? -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 3 févr. 2013 à 09:27, Matt Painter [matt@deity.co.nz](mailto:matt@deity.co.nz) a écrit : Aha, have just discovered the section in the doco about dynamic\_templates with an explicit example featuring multi\_field. Looks like it may be what I'm after? On 3 February 2013 21:19, Matt Painter [matt@deity.co.nz](mailto:matt@deity.co.nz) wrote: > Actually, how would that technique work for faceting data which is almost entirely dynamically-mapped? I only know the fields and field structure at the point of the request for indexing being retrieved and, as far as I know, one can't index both a document and include specific mapping at the same time (maybe? I'm pretty new to Elastic). > > FWIW, my data structure is this: > > class Record { > > // User-supplied JSON metadata > List metadata; > > ... > > other known fields; > } > > where the top-level Record is indexed into Elasticsearch, has a bunch of known fields and a list of arbitrary raw JSON metadata - which is what we need faceting on. > > I realise that not having a known schema is limiting what we can get out of Elasticsearch, but I'm trying to make the barrier for users to index and search on arbitrary content as low as possible. > > M > > On 3 February 2013 21:00, Matt Painter [matt@deity.co.nz](mailto:matt@deity.co.nz) wrote: > > > Thanks for that David - didn't realise that existed. Looks like some fun JSON munging for me! > > > > M > > > > PS. Thanks for the word of warning re: \_all - noted. > > > > On Sunday, February 3, 2013 8:13:45 PM UTC+13, David Pilato wrote: > > > > > I usualy use multifield feature for that. > > > > > > field.field is analyzed > > > field.facet is not analyzed > > > > > > IMHO, using \_all in facets is risky. You could hit some Out Of Memory Exception issues. > > > > > > -- > > > David 😉 > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > > > > Le 3 févr. 2013 à 05:57, Matt Painter [ma...@deity.co.nz](mailto:ma...@deity.co.nz) a écrit : > > > > > > I am developing a system that as well as a core, predefined schema being indexed by elasticsearch, also contains arbitrary user-supplied JSON. I am using the snowball analyser for all data. > > > > > > I am wishing to provide the ability for users to perform a faceted search over any of their arbitrary fields. However because the fields are being indexed using snowball, the terms being retrieved for faceting are incorrect (singular rather than plural in some cases - which is fine - but completely bogus prefixes in others). I was hoping that adding a "\_all" : { "store": "yes" } would do the trick, but no such luck. > > > > > > Is there an easy solution? Or do I need to index each field twice, one wit the snowball analyser (for searching) and one with no analysers (for faceting)? > > > > > > ## M > > > > > > 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). > > -- > Matt Painter > matt@deity.co.nz > +64 21 115 9378 ## -- Matt Painter matt@deity.co.nz +64 21 115 9378 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:** ![nullpainter](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nullpainter/32/2504_2.png) [@nullpainter](https://discuss.elastic.co/u/nullpainter)\ **Post date:** [February 3, 2013, 5:42pm UTC](https://discuss.elastic.co/t/analyzers-and-faceting-and-unknown-data/10606/7 "2013-02-03T17:42:48Z")
Thanks David. Each String of metadata is actually a complete JSON document (multiple fields, arrays, collections, etc.), so applying multi\_field mapping against the metadata field isn't going to work. I went with dynamic\_templates and applied multi\_field to all string fields and all works well thus far - for my test data at least! Cheers, M On 3 February 2013 23:18, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > If your documents look like > { > "metadata":["value1", "value2"...] > } > > You only have to define a mapping for your field metadata using multifield. > > If users will add new fields, like: > > { > "metadata1":"value1", > "metadata2":"value2"... > } > > I think that dynamic\_templates will help. > > How does your JSON doc look like at the end? > > -- > David 😉 > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 3 févr. 2013 à 09:27, Matt Painter [matt@deity.co.nz](mailto:matt@deity.co.nz) a écrit : > > Aha, have just discovered the section in the doco about dynamic\_templateswith an explicit example featuring > multi\_field. Looks like it may be what I'm after? > > On 3 February 2013 21:19, Matt Painter [matt@deity.co.nz](mailto:matt@deity.co.nz) wrote: > > > Actually, how would that technique work for faceting data which is almost > > entirely dynamically-mapped? I only know the fields and field structure at > > the point of the request for indexing being retrieved and, as far as I > > know, one can't index both a document and include specific mapping at the > > same time (maybe? I'm pretty new to Elastic). > > > > FWIW, my data structure is this: > > > > class Record { > > > > // User-supplied JSON metadata > > List metadata; > > > > ... > > > > other known fields; > > } > > > > where the top-level Record is indexed into Elasticsearch, has a bunch of > > known fields and a list of arbitrary raw JSON metadata - which is what we > > need faceting on. > > > > I realise that not having a known schema is limiting what we can get out > > of Elasticsearch, but I'm trying to make the barrier for users to index and > > search on arbitrary content as low as possible. > > > > M > > > > On 3 February 2013 21:00, Matt Painter [matt@deity.co.nz](mailto:matt@deity.co.nz) wrote: > > > > > Thanks for that David - didn't realise that existed. Looks like some fun > > > JSON munging for me! > > > > > > M > > > > > > PS. Thanks for the word of warning re: \_all - noted. > > > > > > On Sunday, February 3, 2013 8:13:45 PM UTC+13, David Pilato wrote: > > > > > > > I usualy use multifield feature for that. > > > > > > > > field.field is analyzed > > > > field.facet is not analyzed > > > > > > > > IMHO, using \_all in facets is risky. You could hit some Out Of Memory > > > > Exception issues. > > > > > > > > -- > > > > David 😉 > > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > > > > > > Le 3 févr. 2013 à 05:57, Matt Painter [ma...@deity.co.nz](mailto:ma...@deity.co.nz) a écrit : > > > > > > > > I am developing a system that as well as a core, predefined schema > > > > being indexed by elasticsearch, also contains arbitrary user-supplied JSON. > > > > I am using the snowball analyser for all data. > > > > > > > > I am wishing to provide the ability for users to perform a faceted > > > > search over any of their arbitrary fields. However because the fields are > > > > being indexed using snowball, the terms being retrieved for faceting are > > > > incorrect (singular rather than plural in some cases - which is fine - but > > > > completely bogus prefixes in others). I was hoping that adding a"\_all" : { "store": "yes" } would > > > > do the trick, but no such luck. > > > > > > > > Is there an easy solution? Or do I need to index each field twice, one > > > > wit the snowball analyser (for searching) and one with no analysers (for > > > > faceting)? > > > > > > > > M > > > > > > > > -- > > > > 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](http://googlegroups.com). > > > > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[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). > > > > -- > > Matt Painter > > matt@deity.co.nz > > +64 21 115 9378 > > -- > Matt Painter > matt@deity.co.nz > +64 21 115 9378 > > -- > 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). -- Matt Painter matt@deity.co.nz +64 21 115 9378 -- 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:53am UTC](https://discuss.elastic.co/t/analyzers-and-faceting-and-unknown-data/10606/8 "2017-07-06T02:53:14Z")