[FEATURE] Better support for reindexing, splitting, cloning etc. workflows #1526
Description
Is your feature request related to a problem?
When upgrading to a new major version, it is necessary to reindex any indices that were created more than 1 major version ago. These indices will likely be more than a couple of years old and probably reaching the end of their lifecycle, however, there is currently no way to reindex these indices and have the new index continue that same lifecycle.
Instead, the newly reindexed/split/cloned index will have the same policy attached and work its way through the lifecycle stages all over again. If the policy has a rollover action then that will immediately fail:
Failed to transition index as min_rollover_age condition was used, but the index has never been rolled over
And conditions like min_index_age and min_rollover_age will be based on the reindexed index's creation date and not that of the original index, which is almost certainly not what the user wants.
What solution would you like?
It would be nice if you could tell ism that the reindexed index should go straight to the warm/cold phase and/or to treat the index as if it was rolled over / created 2 years ago or something.
What alternatives have you considered?
Creating a one-time use policy for every single index that doesn't include rollover and calculates the min_index_age to set for each stage based on how old the old index was but that's really not ideal.
Do you have any additional context?
I think actions like reindexing, splitting, cloning etc. are fairly common operations and ISM should play nicely with them.