123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280 |
- [[search-aggregations-metrics-scripted-metric-aggregation]]
- === Scripted Metric Aggregation
- experimental[]
- A metric aggregation that executes using scripts to provide a metric output.
- Example:
- [source,js]
- --------------------------------------------------
- POST ledger/_search?size=0
- {
- "query" : {
- "match_all" : {}
- },
- "aggs": {
- "profit": {
- "scripted_metric": {
- "init_script" : "params._agg.transactions = []",
- "map_script" : "params._agg.transactions.add(doc.type.value == 'sale' ? doc.amount.value : -1 * doc.amount.value)", <1>
- "combine_script" : "double profit = 0; for (t in params._agg.transactions) { profit += t } return profit",
- "reduce_script" : "double profit = 0; for (a in params._aggs) { profit += a } return profit"
- }
- }
- }
- }
- --------------------------------------------------
- // CONSOLE
- // TEST[setup:ledger]
- <1> `map_script` is the only required parameter
- The above aggregation demonstrates how one would use the script aggregation compute the total profit from sale and cost transactions.
- The response for the above aggregation:
- [source,js]
- --------------------------------------------------
- {
- "took": 218,
- ...
- "aggregations": {
- "profit": {
- "value": 240.0
- }
- }
- }
- --------------------------------------------------
- // TESTRESPONSE[s/"took": 218/"took": $body.took/]
- // TESTRESPONSE[s/\.\.\./"_shards": $body._shards, "hits": $body.hits, "timed_out": false,/]
- The above example can also be specified using file scripts as follows:
- [source,js]
- --------------------------------------------------
- POST ledger/_search?size=0
- {
- "aggs": {
- "profit": {
- "scripted_metric": {
- "init_script" : {
- "file": "my_init_script"
- },
- "map_script" : {
- "file": "my_map_script"
- },
- "combine_script" : {
- "file": "my_combine_script"
- },
- "params": {
- "field": "amount", <1>
- "_agg": {} <2>
- },
- "reduce_script" : {
- "file": "my_reduce_script"
- }
- }
- }
- }
- }
- --------------------------------------------------
- // CONSOLE
- // TEST[setup:ledger]
- <1> script parameters for `init`, `map` and `combine` scripts must be specified
- in a global `params` object so that it can be share between the scripts.
- <2> if you specify script parameters then you must specify `"_agg": {}`.
- ////
- Verify this response as well but in a hidden block.
- [source,js]
- --------------------------------------------------
- {
- "took": 218,
- ...
- "aggregations": {
- "profit": {
- "value": 240.0
- }
- }
- }
- --------------------------------------------------
- // TESTRESPONSE[s/"took": 218/"took": $body.took/]
- // TESTRESPONSE[s/\.\.\./"_shards": $body._shards, "hits": $body.hits, "timed_out": false,/]
- ////
- For more details on specifying scripts see <<modules-scripting, script documentation>>.
- ==== Allowed return types
- Whilst any valid script object can be used within a single script, the scripts must return or store in the `_agg` object only the following types:
- * primitive types
- * String
- * Map (containing only keys and values of the types listed here)
- * Array (containing elements of only the types listed here)
- ==== Scope of scripts
- The scripted metric aggregation uses scripts at 4 stages of its execution:
- init_script:: Executed prior to any collection of documents. Allows the aggregation to set up any initial state.
- +
- In the above example, the `init_script` creates an array `transactions` in the `_agg` object.
- map_script:: Executed once per document collected. This is the only required script. If no combine_script is specified, the resulting state
- needs to be stored in an object named `_agg`.
- +
- In the above example, the `map_script` checks the value of the type field. If the value is 'sale' the value of the amount field
- is added to the transactions array. If the value of the type field is not 'sale' the negated value of the amount field is added
- to transactions.
- combine_script:: Executed once on each shard after document collection is complete. Allows the aggregation to consolidate the state returned from
- each shard. If a combine_script is not provided the combine phase will return the aggregation variable.
- +
- In the above example, the `combine_script` iterates through all the stored transactions, summing the values in the `profit` variable
- and finally returns `profit`.
- reduce_script:: Executed once on the coordinating node after all shards have returned their results. The script is provided with access to a
- variable `_aggs` which is an array of the result of the combine_script on each shard. If a reduce_script is not provided
- the reduce phase will return the `_aggs` variable.
- +
- In the above example, the `reduce_script` iterates through the `profit` returned by each shard summing the values before returning the
- final combined profit which will be returned in the response of the aggregation.
- ==== Worked Example
- Imagine a situation where you index the following documents into and index with 2 shards:
- [source,js]
- --------------------------------------------------
- PUT /transactions/stock/_bulk?refresh
- {"index":{"_id":1}}
- {"type": "sale","amount": 80}
- {"index":{"_id":2}}
- {"type": "cost","amount": 10}
- {"index":{"_id":3}}
- {"type": "cost","amount": 30}
- {"index":{"_id":4}}
- {"type": "sale","amount": 130}
- --------------------------------------------------
- // CONSOLE
- Lets say that documents 1 and 3 end up on shard A and documents 2 and 4 end up on shard B. The following is a breakdown of what the aggregation result is
- at each stage of the example above.
- ===== Before init_script
- No params object was specified so the default params object is used:
- [source,js]
- --------------------------------------------------
- "params" : {
- "_agg" : {}
- }
- --------------------------------------------------
- ===== After init_script
- This is run once on each shard before any document collection is performed, and so we will have a copy on each shard:
- Shard A::
- +
- [source,js]
- --------------------------------------------------
- "params" : {
- "_agg" : {
- "transactions" : []
- }
- }
- --------------------------------------------------
- Shard B::
- +
- [source,js]
- --------------------------------------------------
- "params" : {
- "_agg" : {
- "transactions" : []
- }
- }
- --------------------------------------------------
- ===== After map_script
- Each shard collects its documents and runs the map_script on each document that is collected:
- Shard A::
- +
- [source,js]
- --------------------------------------------------
- "params" : {
- "_agg" : {
- "transactions" : [ 80, -30 ]
- }
- }
- --------------------------------------------------
- Shard B::
- +
- [source,js]
- --------------------------------------------------
- "params" : {
- "_agg" : {
- "transactions" : [ -10, 130 ]
- }
- }
- --------------------------------------------------
- ===== After combine_script
- The combine_script is executed on each shard after document collection is complete and reduces all the transactions down to a single profit figure for each
- shard (by summing the values in the transactions array) which is passed back to the coordinating node:
- Shard A:: 50
- Shard B:: 120
- ===== After reduce_script
- The reduce_script receives an `_aggs` array containing the result of the combine script for each shard:
- [source,js]
- --------------------------------------------------
- "_aggs" : [
- 50,
- 120
- ]
- --------------------------------------------------
- It reduces the responses for the shards down to a final overall profit figure (by summing the values) and returns this as the result of the aggregation to
- produce the response:
- [source,js]
- --------------------------------------------------
- {
- ...
- "aggregations": {
- "profit": {
- "value": 170
- }
- }
- }
- --------------------------------------------------
- ==== Other Parameters
- [horizontal]
- params:: Optional. An object whose contents will be passed as variables to the `init_script`, `map_script` and `combine_script`. This can be
- useful to allow the user to control the behavior of the aggregation and for storing state between the scripts. If this is not specified,
- the default is the equivalent of providing:
- +
- [source,js]
- --------------------------------------------------
- "params" : {
- "_agg" : {}
- }
- --------------------------------------------------
|