mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-10 06:55:32 +00:00
18866c4c0b
This commit changes the format of the `hits.total` in the search response to be an object with a `value` and a `relation`. The `value` indicates the number of hits that match the query and the `relation` indicates whether the number is accurate (in which case the relation is equals to `eq`) or a lower bound of the total (in which case it is equals to `gte`). This change also adds a parameter called `rest_total_hits_as_int` that can be used in the search APIs to opt out from this change (retrieve the total hits as a number in the rest response). Note that currently all search responses are accurate (`track_total_hits: true`) or they don't contain `hits.total` (`track_total_hits: true`). We'll add a way to get a lower bound of the total hits in a follow up (to allow numbers to be passed to `track_total_hits`). Relates #33028
47 lines
1.7 KiB
Plaintext
47 lines
1.7 KiB
Plaintext
[[transform-chain]]
|
|
=== Chain Transform
|
|
|
|
A <<transform, Transform>> that executes an ordered list of configured transforms
|
|
in a chain, where the output of one transform serves as the input of the next
|
|
transform in the chain. The payload that is accepted by this transform serves as
|
|
the input of the first transform in the chain and the output of the last transform
|
|
in the chain is the output of the `chain` transform as a whole.
|
|
|
|
You can use chain transforms to build more complex transforms out of the other
|
|
available transforms. For example, you can combine a <<transform-search, `search`>>
|
|
transform and a <<transform-script, `script`>> transform, as shown in the
|
|
following snippet:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
"transform" : {
|
|
"chain" : [ <1>
|
|
{
|
|
"search" : { <2>
|
|
"indices" : [ "logstash-*" ],
|
|
"body" : {
|
|
"size" : 0,
|
|
"query" : {
|
|
"match" : { "priority" : "error" }
|
|
}
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"script" : "return [ error_count : ctx.payload.hits.total.value ]" <3>
|
|
}
|
|
]
|
|
}
|
|
--------------------------------------------------
|
|
// NOTCONSOLE
|
|
<1> The `chain` transform definition
|
|
<2> The first transform in the chain (in this case, a `search` transform)
|
|
<3> The second and final transform in the chain (in this case, a `script`
|
|
transform)
|
|
|
|
This example executes a `count` search on the cluster to look for `error` events.
|
|
The search results are then passed to the second `script` transform. The `script`
|
|
transform extracts the total hit count and assigns it to the `error_count` field
|
|
in a newly-generated payload. This new payload is the output of the `chain`
|
|
transform and replaces the payload in the watch execution context.
|