[SERVER-66252] Create a way to convert a nonclustered collection to a clustered one Created: 05/May/22 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
We have many internal collections that would benefit from being clustered, but are already in existence. It would be helpful to provide a mechanism for converting the collections on upgrade or with user action. config.transactions, findAndModify image collections, and all of replication's and sharding's metadata collections all seem like reasonable candidates. |