Allow defining index name/alias(es) on index upgrade #36390
Labels
enhancement
New value added to drive a business result
Feature:Upgrade Assistant
Team:Kibana Management
Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Describe the feature:
This seems to be purely cosmetic at this time. Administrators who have a very specific index naming system may be frustrated by the default values.
Describe a specific use case for the feature:
After, recently upgraded elasticsearch and kibana from 6.x to 7.0.1, I checked out the "8.0 Upgrade Assistant" from the Management section. It reported that my index was created with an older version, and suggested I reindex after a backup, which I performed.
Due to the need to change a field from auto-discovered integer to float, a relatively common problem newbies like me might encounter, I had already adopted a new naming convention and reindexed in the past. I chose the naming convention of indexname_vn, where n indicates the version. The intent is to have a base name always represented by an alias to indexname, with the underlying index able to increment revisions as needed.
During the process, the upgrade process flawlessly recreated my index, using aliases to ensure functionality. In this case, the default naming convention caused a break in my preferred convention. Instead of using indexname_v[n+1], as I would have preferred if I were able to make the decision myself, it created an index with name reindexed-v7-indexname_v2, with two aliases: indexname and indexname_v2.
The end state I would have preferred is to simply have indexname_v3 with a single alias, indexname. If I were able to select the destination index name, and perhaps alias names as well, the end state would have been cleaner.
The text was updated successfully, but these errors were encountered: