L3 - Default As part of OPT-3188, we will create a new index to store completed activities from the engine. This has the potential to be a large index, so we should consider allowing for this. In addition or instead of splitting by a sensible property (OPT-3190), we should also consider adding partitioning/rolling over of this index based on size/date. We do something similar for the event index, so perhaps we could reuse some of the code from there.
AT:
- We rollover the activity index/indices based on size or date
- We can still retrieve results from multiple indices in the event of a rolled over index