have you seen the rollover API - you might want to take a look at index lifecycle management and frozen indices as well in order to reduce memory footprint.
sure, we're actually using the rollover API for our regular indexes, thru the "index lifecycle management".
the challenge we have is combining the 2...
as far as we see, the "rollup_index": "" (in the rollup definition) needs to be set to a static index name (no variable or alias, we tried either and it failed)..
so again to clarify, we love the ILP idea, and want to extand this "set and forget" concept also to our rollup's but we are stuck here...
does my question make more sense now?
do you have any insight when above may be implemented?
I was hoping someone out there has some better solution.
On another thought, can we maybe use the transform api? So to concentrate the data in 5 min buckets into a new index then this new index is a regular (non roll-up) index therefore the ILP rollover should work as usual.
Does this make sense? Or is my understanding of transform incorrect... (or maybe some other solution chaining....)
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.