You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To keep docs reasonably small we omit fields that has zero value, but when we use avg or extended_stats aggregation it would be nice to make missing values assumed to be zeroes too.
In example below we have 31 970 816 docs in bucket, but only 7 310 of them have non-zero value.
I was about to sumitba request on this too.
Imi would suggest that anyvaggregation operating on a field should have missing option. If specified, aggregation should accumulate missing values under that value and honor any nested aggregations within. It should never assume any value like 0 since it may clash with actual keys.
I was planning to show examples of enormous query that is needed for a two lecel aggregation that has to cover all values including missing and other for both levels using missing aggregation. It can be done but not only the query is huge and highly repetitive the result need to be heavily processed to move second level keys nested under missing agg into the first level buckets.
Please please do implement missing as an option in all bucketing aggs!
I am not even asking to have an option to also aggregare other - keys that were not used due to size parameter although it would be veru useful :-)
To keep docs reasonably small we omit fields that has zero value, but when we use
avg
orextended_stats
aggregation it would be nice to make missing values assumed to be zeroes too.In example below we have 31 970 816 docs in bucket, but only 7 310 of them have non-zero value.
Maybe additional boolean parameter could be introduced for
extended_stats
andavg
aggregations, likeassume_zeroes
?cc @uboness
The text was updated successfully, but these errors were encountered: