From e3543b06ba3097c31b32f3db4f039e4ec4286814 Mon Sep 17 00:00:00 2001 From: Zachary Tong Date: Fri, 23 Feb 2018 23:20:45 +0000 Subject: [PATCH] [Docs] Remove bad cross-book link Temporary to keep the build green, will figure this out during the next round of rollup docs work. Original commit: elastic/x-pack-elasticsearch@7657938ffbfa413c0df1b5ae005aa4b32ceaf2c9 --- docs/en/rest-api/rollup/rollup-job-config.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/rest-api/rollup/rollup-job-config.asciidoc b/docs/en/rest-api/rollup/rollup-job-config.asciidoc index 310a1ab6f7d..fd5c96a5aa8 100644 --- a/docs/en/rest-api/rollup/rollup-job-config.asciidoc +++ b/docs/en/rest-api/rollup/rollup-job-config.asciidoc @@ -72,7 +72,7 @@ In the above example, there are several pieces of logistical configuration for t the job's indexer. When the interval triggers, the indexer will attempt to rollup the data in the index pattern. The cron pattern is unrelated to the time interval of the data being rolled up. For example, you may wish to create hourly rollups of your document (as defined in the <>) but to only run the indexer on a daily basis at midnight, as defined by the cron. - The cron pattern is defined just like Watcher's {xpack-ref}/watcher/trigger/schedule/cron.html[Cron Schedule]. + The cron pattern is defined just like Watcher's Cron Schedule. `size` (required):: (int) The number of bucket results that should be processed on each iteration of the rollup indexer. A larger value