I am new to ES and evaluating ES for its analytic strengths.
Based on documentation i have read so far, the cardinality agg is not
accurate.
What i want to find out is that if the other aggs are accurate or not?
Especially with Filters applied.
If by default they are not accurate is there a work around to get accuracy
in the ES queries.
The terms, cardinality, percentiles and geo_hash grid aggregations trade
accuracy for speed/memory , you can expect other aggregations to return
accurate results.
On Mon, Dec 22, 2014 at 7:51 PM, vijay arora arorav@uw.edu wrote:
I am new to ES and evaluating ES for its analytic strengths.
Based on documentation i have read so far, the cardinality agg is not
accurate.
What i want to find out is that if the other aggs are accurate or not?
Especially with Filters applied.
If by default they are not accurate is there a work around to get accuracy
in the ES queries.
I think the key part of the question here is about filters? Filters are
always up to date modulo refresh interval. Its pretty efficient because
Lucene's segments are immutable so once a filter has been applied to a
segment you can cache its results and merge it with the deletes list to
have for as long as you have the memory to keep the cache around.
The terms, cardinality, percentiles and geo_hash grid aggregations trade
accuracy for speed/memory , you can expect other aggregations to return
accurate results.
On Mon, Dec 22, 2014 at 7:51 PM, vijay arora arorav@uw.edu wrote:
I am new to ES and evaluating ES for its analytic strengths.
Based on documentation i have read so far, the cardinality agg is not
accurate.
What i want to find out is that if the other aggs are accurate or not?
Especially with Filters applied.
If by default they are not accurate is there a work around to get
accuracy in the ES queries.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.