Well, my use case says I have tens of thousands of records for each members. I want to do a simple terms aggs on member ID. If my count of member ID remains same throughout .. good enough, if the number of members keep on increasing, day by day ES has to keep more and more data into memory to calculate the aggs. Does not sound very promising. What we do is implementation of routing to put member specific data into a particular shard. Why can't aggs be based on shard based calculations so that I am safe from loading tons of data into memory.
Any thoughts? On Sunday, 9 November 2014 22:58:12 UTC+5:30, pulkitsinghal wrote: > > Sharing a response I received from Igor Motov: > > "scroll works only to page results. paging aggs doesn't make sense since >> aggs are executed on the entire result set. therefore if it managed to fit >> into the memory you should just get it. paging will mean that you throw >> away a lot of results that were already calculated. the only way to "page" >> is by limiting the results that you are running aggs on. for example if >> your data is sorted by date and you want to build histogram for the results >> one date range at a time." > > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f6307a18-ea96-403d-ac02-dc37d3f2cceb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
