# Potential Feature Request: Allow choosing index name on reindex operation

**URL:** <https://discuss.elastic.co/t/potential-feature-request-allow-choosing-index-name-on-reindex-operation/180417>\
**Category:** Kibana\
**Created:** [May 9, 2019, 5:23pm UTC](https://discuss.elastic.co/t/potential-feature-request-allow-choosing-index-name-on-reindex-operation/180417 "2019-05-09T17:23:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![d.neri](https://avatars.discourse-cdn.com/v4/letter/d/bc8723/32.png) [@d.neri](https://discuss.elastic.co/u/d.neri)\
**Post date:** [May 9, 2019, 5:23pm UTC](https://discuss.elastic.co/t/potential-feature-request-allow-choosing-index-name-on-reindex-operation/180417/1 "2019-05-09T17:23:21Z")

</div>

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.

During the process, it flawlessly recreated my index, using aliases to ensure functionality. However, I had already recreated the index myself in the past, adopting a naming format of _indexname\_vn_,  
where _n_ indicates the version. (This was due to the need to change a field from auto-discovered integer to float, a relatively common problem newbies like me might encounter.) I then manually create an alias _indexname_ to reference the original usage before adopting the naming format and thereby preserving functionality.

In this case, the automatic index recreation muddied the waters a bit. 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 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. To be clear, there appears to be ZERO functionality loss at this time, and this is essentially cosmetic.

---

<div class="post-metadata">

**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\
**Post date:** [May 9, 2019, 5:31pm UTC](https://discuss.elastic.co/t/potential-feature-request-allow-choosing-index-name-on-reindex-operation/180417/2 "2019-05-09T17:31:26Z")

</div>

Sounds like an interesting enhance. Please post feature requests to [https://github.com/elastic/kibana/issues/new?template=Feature\_request.md](https://github.com/elastic/kibana/issues/new?template=Feature_request.md)

---

<div class="post-metadata">

**Author:** ![d.neri](https://avatars.discourse-cdn.com/v4/letter/d/bc8723/32.png) [@d.neri](https://discuss.elastic.co/u/d.neri)\
**Post date:** [May 9, 2019, 6:07pm UTC](https://discuss.elastic.co/t/potential-feature-request-allow-choosing-index-name-on-reindex-operation/180417/3 "2019-05-09T18:07:44Z")

</div>

Done! Filed as [https://github.com/elastic/kibana/issues/36390](https://github.com/elastic/kibana/issues/36390). Thanks for validating.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 6, 2019, 6:08pm UTC](https://discuss.elastic.co/t/potential-feature-request-allow-choosing-index-name-on-reindex-operation/180417/4 "2019-06-06T18:08:56Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
