[SERVER-7337] Need the ability to rename an index once it has been created Created: 12/Oct/12 Updated: 06/Dec/22 Resolved: 11/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 8 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
If a customer has a need to rename an index, to keep databases structurally identical across test and production environments for example, it is currently not possible. Using ensureIndex() with a different name will will fail silently, and manually updating the system.indexes collection is not possible or recommended. This means that a customer has no option but to drop and recreate an index in order to change its name. |
| Comments |
| Comment by Connie Chen [ 11/May/20 ] |
|
We will not be doing this, the workaround is to drop the index and rebuild it with a new name. |
| Comment by Eric Milkie [ 09/Aug/19 ] |
|
We won't be considering this work until we can introduce an internal identifier like a UUID to uniquely identify indexes other than by using their names. |