|
@@ -33,7 +33,7 @@ live?
|
|
|
|
|
|
|
|
==== Request Body
|
|
==== Request Body
|
|
|
|
|
|
|
|
-There is no request body for the Get Jobs API.
|
|
|
|
|
|
|
+There is no request body for the Get Rollup Caps API.
|
|
|
|
|
|
|
|
==== Authorization
|
|
==== Authorization
|
|
|
|
|
|
|
@@ -179,4 +179,4 @@ GET _xpack/rollup/data/sensor-1
|
|
|
Why is this? The original rollup job was configured against a specific index pattern (`sensor-*`) not a concrete index
|
|
Why is this? The original rollup job was configured against a specific index pattern (`sensor-*`) not a concrete index
|
|
|
(`sensor-1`). So while the index belongs to the pattern, the rollup job is only valid across the entirety of the pattern
|
|
(`sensor-1`). So while the index belongs to the pattern, the rollup job is only valid across the entirety of the pattern
|
|
|
not just one of it's containing indices. So for that reason, the Rollup Capabilities API only returns information based
|
|
not just one of it's containing indices. So for that reason, the Rollup Capabilities API only returns information based
|
|
|
-on the originally configured index name or pattern.
|
|
|
|
|
|
|
+on the originally configured index name or pattern.
|
David Kyle