Min aggregation
editMin aggregation
editA single-value
metrics aggregation that keeps track and returns the minimum
value among numeric values extracted from the aggregated documents. These
values can be extracted either from specific numeric fields in the documents,
or be generated by a provided script.
The min
and max
aggregation operate on the double
representation of
the data. As a consequence, the result may be approximate when running on longs
whose absolute value is greater than 2^53
.
Computing the min price value across all documents:
POST /sales/_search?size=0 { "aggs": { "min_price": { "min": { "field": "price" } } } }
Response:
{ ... "aggregations": { "min_price": { "value": 10.0 } } }
As can be seen, the name of the aggregation (min_price
above) also serves as
the key by which the aggregation result can be retrieved from the returned
response.
Script
editThe min
aggregation can also calculate the minimum of a script. The example
below computes the minimum price:
POST /sales/_search { "aggs": { "min_price": { "min": { "script": { "source": "doc.price.value" } } } } }
This will use the Painless scripting language and no script parameters. To use a stored script use the following syntax:
POST /sales/_search { "aggs": { "min_price": { "min": { "script": { "id": "my_script", "params": { "field": "price" } } } } } }
Value Script
editLet’s say that the prices of the documents in our index are in USD, but we would like to compute the min in EURO (and for the sake of this example, let’s say the conversion rate is 1.2). We can use a value script to apply the conversion rate to every value before it is aggregated:
POST /sales/_search { "aggs": { "min_price_in_euros": { "min": { "field": "price", "script": { "source": "_value * params.conversion_rate", "params": { "conversion_rate": 1.2 } } } } } }
Missing value
editThe missing
parameter defines how documents that are missing a value should
be treated. By default they will be ignored but it is also possible to treat
them as if they had a value.
Histogram fields
editWhen min
is computed on histogram fields, the result of the aggregation is the minimum
of all elements in the values
array. Note, that the counts
array of the histogram is ignored.
For example, for the following index that stores pre-aggregated histograms with latency metrics for different networks:
PUT metrics_index/_doc/1 { "network.name" : "net-1", "latency_histo" : { "values" : [0.1, 0.2, 0.3, 0.4, 0.5], "counts" : [3, 7, 23, 12, 6] } } PUT metrics_index/_doc/2 { "network.name" : "net-2", "latency_histo" : { "values" : [0.1, 0.2, 0.3, 0.4, 0.5], "counts" : [8, 17, 8, 7, 6] } } POST /metrics_index/_search?size=0 { "aggs" : { "min_latency" : { "min" : { "field" : "latency_histo" } } } }
The min
aggregation will return the minimum value of all histogram fields:
{ ... "aggregations": { "min_latency": { "value": 0.1 } } }