[SERVER-30856] Create Easy Way to Change Shard Key Created: 26/Aug/17 Updated: 20/Sep/17 Resolved: 26/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Sharding |
| Affects Version/s: | 3.4.7 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Rice | Assignee: | Kelsey Schubert |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
This case covers making it easy for users to change a shard key. In an abstract sense, this would be automation of something that can already be done by very laborious sets of work-by-hand. db.runCommand() for this "changeShardKey" runs in config or admin database.
All other collections in the database would be copied as-is The steps involved are: This should be a fairly common use case and should not require dumping the entire database to disk with mongodump / mongoexport. |
| Comments |
| Comment by Kelsey Schubert [ 26/Aug/17 ] |
|
Thank you for the feature request. We're tracking the work to provide a command to change the shard key of a collection in Kind regards, |