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
In Elasticsearch there are two histogram algorithms available: tdigest and hdr. The histogram field mapper is algorithm agnostic. A tdigest or hdr histogram can be stored in a field mapped as histogram. However the features using the histogram field like aggregations don't know what kind of histogram is stored in a histogram field. So it is possible to run a percentile aggregation configured with tdigest on a histogram field that stores a hdr histogram. The result that gets produced will not be useful at all. Ideally this shouldn't be allowed. But today this validation doesn't occur because the field mapper doesn't record what algorithm is used.
Additionally downsampling needs to know what algorithm is used, otherwise downsampling can't merge histograms. This is the reason why today downsampling doesn't support metric fields of type histogram.
The proposal is to add an algorithm attribute to the histogram field type. So that other features can make use of that. I don't think we can make this a required argument for bwc reasons from the start (but maybe many versions from now).
In Elasticsearch there are two histogram algorithms available: tdigest and hdr. The histogram field mapper is algorithm agnostic. A tdigest or hdr histogram can be stored in a field mapped as histogram. However the features using the histogram field like aggregations don't know what kind of histogram is stored in a histogram field. So it is possible to run a percentile aggregation configured with
tdigest
on a histogram field that stores a hdr histogram. The result that gets produced will not be useful at all. Ideally this shouldn't be allowed. But today this validation doesn't occur because the field mapper doesn't record what algorithm is used.Additionally downsampling needs to know what algorithm is used, otherwise downsampling can't merge histograms. This is the reason why today downsampling doesn't support metric fields of type histogram.
The proposal is to add an algorithm attribute to the histogram field type. So that other features can make use of that. I don't think we can make this a required argument for bwc reasons from the start (but maybe many versions from now).
Relates to #74213
The text was updated successfully, but these errors were encountered: