There's no aggregation in percolation queries and we only percolate new documents, the flow is as follow :
Step 1 : data logging 1. An event occures 2. possible ES search queries with or without facet on different indices 3. ES percolation query with event data on the tester index (5 queries stored, no other data) 4. event data logging in a plain text file Step 2 : defered data indexing 1. logstash detects the new event and send it to a centralized redis queue like the centralized example described in logstash documentation 2. logstash parses the queue and indexes the event in ES Meanwhile, there can be aggregation queries on the stat part of the application but their rate is minimal compared to the insert rate. Le mercredi 19 mars 2014 11:01:16 UTC+1, Lee Hinman a écrit : > > On 3/18/14, 5:58 AM, Dunaeth wrote: > > Actually, tester is a dedicated percolator index with 5 percolation > > queries stored and no other data. Percolated documents are web logs and > > the tester mapping is (elided) > > Are you doing aggregations when you percolate documents? Are you > percolating existing documents or sending new ones every time? > > ;; Lee > > -- 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/596f7efa-11e6-4045-a4bc-9200cb535b37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
