Hi Guys,
Would it make sense to set "doc_values: enabled" on a murmur3 type field since it’s being used for aggregations?
--
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 .
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/34629D7E-3B3C-4B18-B13E-5A689792CFE8%40venarc.com .
For more options, visit https://groups.google.com/d/optout .
warkolm
(Mark Walkom)
March 26, 2015, 12:17am
2
Here's some info on doc values
http://www.elastic.co/guide/en/elasticsearch/guide/current/doc-values.html#_enabling_doc_values
I'm not sure what a murmur3 field is though, I can see what it is but how
does that relate to ES?
On 26 March 2015 at 10:28, Drew Kutcharian drew@venarc.com wrote:
Hi Guys,
Would it make sense to set "doc_values: enabled" on a murmur3 type field
since it’s being used for aggregations?
--
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 .
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/34629D7E-3B3C-4B18-B13E-5A689792CFE8%40venarc.com
.
For more options, visit https://groups.google.com/d/optout .
--
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 .
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-oVq4gGahpU3ymvTR095gZtXsPxe4wY12y0S5yA%2BT9PQ%40mail.gmail.com .
For more options, visit https://groups.google.com/d/optout .
Hi Mark,
Thanks for the reply, but I already know what doc_values are. I wanted to see if there is a benefit to setting murmur3 type (which actually extends long type) to doc_values when it comes to doing cardinality aggregations.
On Mar 25, 2015, at 5:17 PM, Mark Walkom markwalkom@gmail.com wrote:
Here's some info on doc values http://www.elastic.co/guide/en/elasticsearch/guide/current/doc-values.html#_enabling_doc_values http://www.elastic.co/guide/en/elasticsearch/guide/current/doc-values.html#_enabling_doc_values
I'm not sure what a murmur3 field is though, I can see what it is but how does that relate to ES?
On 26 March 2015 at 10:28, Drew Kutcharian <drew@venarc.com mailto:drew@venarc.com > wrote:
Hi Guys,
Would it make sense to set "doc_values: enabled" on a murmur3 type field since it’s being used for aggregations?
--
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%2Bunsubscribe@googlegroups.com .
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/34629D7E-3B3C-4B18-B13E-5A689792CFE8%40venarc.com https://groups.google.com/d/msgid/elasticsearch/34629D7E-3B3C-4B18-B13E-5A689792CFE8%40venarc.com .
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout .
--
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/CAEYi1X-oVq4gGahpU3ymvTR095gZtXsPxe4wY12y0S5yA%2BT9PQ%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-oVq4gGahpU3ymvTR095gZtXsPxe4wY12y0S5yA%2BT9PQ%40mail.gmail.com?utm_medium=email&utm_source=footer .
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout .
--
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 .
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1F1B0539-1E77-477F-80D7-FEB397553E5E%40venarc.com .
For more options, visit https://groups.google.com/d/optout .
I'm answering my own question here since I came across this issue on GitHub.
opened 04:51PM - 07 Apr 15 UTC
closed 04:49AM - 24 Apr 15 UTC
>enhancement
v2.0.0-beta1
:Search/Mapping
I don't think we should allow trappy options like indexed=true or docvalues=fals… e for this field. Cardinality and range of values is enormous by definition.
So the correct field options for a murmur3 field are:
"index" : "no",
"doc_values" : true
On Wednesday, March 25, 2015 at 4:28:25 PM UTC-7, Drew wrote:
Hi Guys,
Would it make sense to set "doc_values: enabled" on a murmur3 type field
since it’s being used for aggregations?
--
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 .
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/294f18cc-45d2-4463-80b0-d47910a8a32f%40googlegroups.com .
For more options, visit https://groups.google.com/d/optout .