Hello, So by writing a plugin you can create a custom aggregation.[1]
I'd like to explore what we could do with that. Why? I'm looking for ways round a costly scan-and-update-each-document algorithm. Do Aggregators run in a parallel fashion, with your aggregation being run against all shards at once? Or do they go through the shards sequentially? How does an Aggregator run only-once for each matching document? I.e. if we have a shard replicated on 3 nodes... Does the aggregation pick one node for that shard? Or does it build up in memory a set of seen documents to avoid duplicating? What happens if you make calls to ElasticSearch from within an Aggregator? Such as updating a document. What about updating the context document that the Aggregator is looking at then-and-there -- could that be done efficiently from within the Aggregator? If so, would you & could you override something in the Aggregator class so it runs over every copy of every document? Thank you for any help with these questions! Best regards, - Daniel 1: https://groups.google.com/forum/#!searchin/elasticsearch/aggregations/elasticsearch/0UYLbyeWiw4/RlSnJtgDj0AJ -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a635a37d-7acd-4ca3-af00-dea882ed27ae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
