123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196 |
- [[search-aggregations-metrics-min-aggregation]]
- === Min aggregation
- ++++
- <titleabbrev>Min</titleabbrev>
- ++++
- A `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.
- NOTE: 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:
- [source,console]
- --------------------------------------------------
- POST /sales/_search?size=0
- {
- "aggs": {
- "min_price": { "min": { "field": "price" } }
- }
- }
- --------------------------------------------------
- // TEST[setup:sales]
- Response:
- [source,console-result]
- --------------------------------------------------
- {
- ...
- "aggregations": {
- "min_price": {
- "value": 10.0
- }
- }
- }
- --------------------------------------------------
- // TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
- 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
- The `min` aggregation can also calculate the minimum of a script. The example
- below computes the minimum price:
- [source,console]
- --------------------------------------------------
- POST /sales/_search
- {
- "aggs": {
- "min_price": {
- "min": {
- "script": {
- "source": "doc.price.value"
- }
- }
- }
- }
- }
- --------------------------------------------------
- // TEST[setup:sales]
- This will use the <<modules-scripting-painless, Painless>> scripting language
- and no script parameters. To use a stored script use the following syntax:
- [source,console]
- --------------------------------------------------
- POST /sales/_search
- {
- "aggs": {
- "min_price": {
- "min": {
- "script": {
- "id": "my_script",
- "params": {
- "field": "price"
- }
- }
- }
- }
- }
- }
- --------------------------------------------------
- // TEST[setup:sales,stored_example_script]
- ==== Value Script
- Let'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:
- [source,console]
- --------------------------------------------------
- POST /sales/_search
- {
- "aggs": {
- "min_price_in_euros": {
- "min": {
- "field": "price",
- "script": {
- "source": "_value * params.conversion_rate",
- "params": {
- "conversion_rate": 1.2
- }
- }
- }
- }
- }
- }
- --------------------------------------------------
- // TEST[setup:sales]
- ==== Missing value
- The `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.
- [source,console]
- --------------------------------------------------
- POST /sales/_search
- {
- "aggs": {
- "grade_min": {
- "min": {
- "field": "grade",
- "missing": 10 <1>
- }
- }
- }
- }
- --------------------------------------------------
- // TEST[setup:sales]
- <1> Documents without a value in the `grade` field will fall into the same
- bucket as documents that have the value `10`.
- [[search-aggregations-metrics-min-aggregation-histogram-fields]]
- ==== Histogram fields
- When `min` is computed on <<histogram,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:
- [source,console]
- --------------------------------------------------
- PUT metrics_index/_doc/1
- {
- "network.name" : "net-1",
- "latency_histo" : {
- "values" : [0.1, 0.2, 0.3, 0.4, 0.5], <1>
- "counts" : [3, 7, 23, 12, 6] <2>
- }
- }
- PUT metrics_index/_doc/2
- {
- "network.name" : "net-2",
- "latency_histo" : {
- "values" : [0.1, 0.2, 0.3, 0.4, 0.5], <1>
- "counts" : [8, 17, 8, 7, 6] <2>
- }
- }
- 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:
- [source,console-result]
- --------------------------------------------------
- {
- ...
- "aggregations": {
- "min_latency": {
- "value": 0.1
- }
- }
- }
- --------------------------------------------------
- // TESTRESPONSE[skip:test not setup]
|