Hard to tell. There are lots of things we would like to clean up for 2.0 and we only started efforts towards that direction (that is why you see more 2.0-only issues on Github these days than in the last months), so it will certainly take time.
On Tue, Nov 18, 2014 at 12:54 PM, Grauen <[email protected]> wrote: > Thanks for Your answer. Do you have any clue when 2.0 will be released? > > Sincerly > > Grauen > > Am Dienstag, 18. November 2014 12:27:05 UTC+1 schrieb Adrien Grand: >> >> I believe this would be addressed through https://github.com/ >> elasticsearch/elasticsearch/issues/8110. >> >> Another option would be to adopt a more entity-centric way of indexing >> your documents by having one document per callingId and updating it every >> time that you get a new event (so that your index contains only one >> document per callingId). >> >> On Tue, Nov 18, 2014 at 11:41 AM, Grauen <[email protected]> >> wrote: >> >>> I calculate the duration of my service-processes using the >>> SUM-Aggregation. Each step of the executed process will be saved in >>> Elasticsearch under a calling Id. >>> >>> This is what I monitor: >>> >>> Duration of Request-Processing for ID #123 (calling service #1) >>> Duration of Server-Response for ID #123 (calling service #1) >>> **Complete Duration for ID #123** >>> >>> Duration of Request-Processing for ID #124 (calling service #1) >>> Duration of Server-Response for ID #124 (calling service #1) >>> **Complete duration for ID #124** >>> >>> Filter: >>> >>> { >>> "from" : 0, "size" :0, >>> >>> "query" : { >>> "filtered" : { >>> "query" : { "match_all" : {}}, >>> "filter" : { >>> "term" : { >>> "callingId" : "123", >>> } >>> } >>> } >>> }, >>> "aggs" : { >>> "total_duration" : { "sum" : { "field" : "duration" } }, >>> "max_duration":{"max": {"field":"duration"}}, >>> "min_duration":{"min":{"field":"duration"}} >>> } >>> } >>> } >>> >>> >>> This returns the complete duration of the process and also tells me >>> which part of the process was the fastest ans which part was the slowest. >>> >>> Next I want to calculate the average *duration of all finished >>> processes* by serviceId. In this case I only care about the total >>> duration for each service, so I can comepare them. >>> >>> Is it possible to create a average, maximum and minimum from all >>> total_durations? >>> >>> -- >>> 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/c20c4d79-cab0-4086-bcdd-574b4d102567% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/elasticsearch/c20c4d79-cab0-4086-bcdd-574b4d102567%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Adrien Grand >> > -- > 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/aad9c8d7-43f6-4d82-986c-d0afe60cf46c%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/aad9c8d7-43f6-4d82-986c-d0afe60cf46c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Adrien Grand -- 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/CAL6Z4j5Pj99_t4wsb0137ZP90mJ7Au50%3DCakim3ZV-xbMSuJHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
