[SERVER-26929] Make all sharding legacy cloner commands include the namespace Created: 07/Nov/16 Updated: 19/Nov/16 Resolved: 07/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.4.0-rc2 |
| Fix Version/s: | 3.4.0-rc3 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2016-11-21 |
| Participants: |
| Description |
|
Since up until mongodb 3.4 sharding only supported a single migration at a time, none of the migration cloner commands include the namespace, which is being migrated. If we decide to do multiple migrations per node in 3.6, our life will be made much easier if we start including the collection namespace in 3.4. |
| Comments |
| Comment by Githook User [ 07/Nov/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |