Search rolled-up data
Deprecated /{index}/_rollup_search The rollup search endpoint is needed because, internally, rolled-up documents utilize a different document structure than the original data. It rewrites standard Query DSL into a format that matches the rollup documents then takes the response and rewrites it back to what a client would expect given the original query.
The request body supports a subset of features from the regular search API. The following functionality is not available:
size: Because rollups work on pre-aggregated data, no search hits can be returned and so size must be set to zero or omitted entirely.
highlighter, suggestors, post_filter, profile, explain: These are similarly disallowed.
For more detailed examples of using the rollup search API, including querying rolled-up data only or combining rolled-up and live data, refer to the External documentation.
Parameters
path Path Parameters
| Name | Type |
|---|---|
index
required
A comma-separated list of data streams and indices used to limit the request. This parameter has the following rules:
| type TypesIndices = type TypesIndexName = string | type TypesIndexName = string[] |
query Query Parameters
| Name | Type |
|---|---|
rest_total_hits_as_int Indicates whether hits.total should be rendered as an integer or an object in the rest search response | boolean |
typed_keys Specify whether aggregation and suggester names should be prefixed by their respective types in the response | boolean |
Request Body
Responses
took: number;
timed_out: boolean;
terminated_early?: boolean;
_shards:
hits:
aggregations?: { };
}