[DOCS-13880] Source and target database primary shards should match when renaming unsharded collections Created: 18/Sep/20 Updated: 30/Oct/23 Due: 16/Jul/21 Resolved: 13/Jul/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Alison Huh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | quick-win | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 2 years, 28 weeks, 5 days ago | ||||||||
| Epic Link: | DOCSP-11701 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
DescriptionThe renameCollection documentation is not mentioning a current limitation in sharded clusters: it is not supported the rename of an unsharded collection if source and target database primary shards are different. There is also a test showing that this scenario is expected to fail. The following sentence should be reformulated. FROM: TO something like: "You cannot rename a sharded collection. You can however rename an unsharded collection in a sharded cluster as long as source and target databases are residing on the same primary shard." Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 23/Jul/21 ] |
|
Author: {'name': 'alisonjhuh', 'email': 'alison.huh@mongodb.com'}Message: |
| Comment by Githook User [ 13/Jul/21 ] |
|
Author: {'name': 'alisonjhuh', 'email': 'alison.huh@mongodb.com'}Message: |
| Comment by Githook User [ 13/Jul/21 ] |
|
Author: {'name': 'alisonjhuh', 'email': 'alison.huh@mongodb.com'}Message: |
| Comment by Githook User [ 13/Jul/21 ] |
|
Author: {'name': 'alisonjhuh', 'email': 'alison.huh@mongodb.com'}Message: |
| Comment by Pierlauro Sciarelli [ 12/Jul/21 ] |
|
Hey naomi.pentrel, the original description of this ticket still holds for v4.4. However, starting from v5.0 - that supports sharded collections rename - the sentence should be rewritten as follows (or in a similar form): "You can rename an unsharded collection in a sharded cluster as long as source and target databases are residing on the same primary shard. It is not supported rename between databases of sharded collections." |