Do Rollup jobs ever reduce in size on their own? I couldn't find a way to add the index created by a rollup job to a lifecycle policy. The rollup job never seemed to reduce in size so I turned the job off.
Need case: we have many watchers routinely query an existing index, making multiple aggregations before processing them, looking for actions to do on their results. We're trying to create a rollup job do the aggregations and have the watchers query the resulting rollup index (it will be much less watchers needed if we can do this).
Should we be using transforms instead?