Hi Dror,
On Tue, Nov 25, 2014 at 2:29 PM, Dror Atariah dror...@gmail.com wrote:
Hi Adrien,
I have two comments/questions:
1) For me, the documentation is still somehow confusing, and the
difference between the *cardinality* and *value_count* aggregations is
not 100% clear.
I have to
Thanks for your quick reply!
On Tue, Nov 25, 2014 at 6:41 PM, Adrien Grand
adrien.gr...@elasticsearch.com wrote:
On Tue, Nov 25, 2014 at 2:29 PM, Dror Atariah dror...@gmail.com wrote:
1) For me, the documentation is still somehow confusing, and the
difference between the *cardinality* and
Hi Henrik,
Indeed, there is no way to compute exact unique counts. The reason why we
don't expose such a feature is that it would be very costly. In your case,
the cardinality is not too large so the terms aggregation helped compute
the number of unique values but if the actual cardinality had
Ah, so there is currently not easy way of getting exact unique counts out
of elasticsearch?
I found a manual way of doing it:
curl -s 'http://localhost:9200/twitter-2014.03.26/_search' -d '{ facets:
{ a: { terms: { field: screen_name, size:
20},facet_filter: {query: {term: {lang:
Hi,
I'm trying out the new cardinality aggregation, and want to measure the
accuracy on my data. I'm using a dataset of a day of sample tweets (2.8m
tweets).
I'm counting the number of unique usernames per language.
To get my reference unique count I use this:
GET /twitter-2014.03.26/_search
{
I don't believe value_count is intended to be a unique count.
On Friday, March 28, 2014 7:17:47 AM UTC, Henrik Nordvik wrote:
Hi,
I'm trying out the new cardinality aggregation, and want to measure the
accuracy on my data. I'm using a dataset of a day of sample tweets (2.8m
tweets).
value_count is the total number of values extracted per bucket. This
example might help:
https://gist.github.com/bly2k/9843335
--
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,
