You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specification/rollup/rollup_search/RollupSearchRequest.ts
+2-25Lines changed: 2 additions & 25 deletions
Original file line number
Diff line number
Diff line change
@@ -35,36 +35,13 @@ import { Dictionary } from '@spec_utils/Dictionary'
35
35
* `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.
36
36
* `highlighter`, `suggestors`, `post_filter`, `profile`, `explain`: These are similarly disallowed.
37
37
*
38
-
* **Searching both historical rollup and non-rollup data**
38
+
* 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.
39
39
*
40
-
* The rollup search API has the capability to search across both "live" non-rollup data and the aggregated rollup data.
41
-
* This is done by simply adding the live indices to the URI. For example:
42
-
*
43
-
* ```
44
-
* GET sensor-1,sensor_rollup/_rollup_search
45
-
* {
46
-
* "size": 0,
47
-
* "aggregations": {
48
-
* "max_temperature": {
49
-
* "max": {
50
-
* "field": "temperature"
51
-
* }
52
-
* }
53
-
* }
54
-
* }
55
-
* ```
56
-
*
57
-
* The rollup search endpoint does two things when the search runs:
58
-
*
59
-
* * The original request is sent to the non-rollup index unaltered.
60
-
* * A rewritten version of the original request is sent to the rollup index.
61
-
*
62
-
* When the two responses are received, the endpoint rewrites the rollup response and merges the two together.
63
-
* During the merging process, if there is any overlap in buckets between the two responses, the buckets from the non-rollup index are used.
0 commit comments