[SERVER-33724] Track unsharded collection creation by commands Created: 07/Mar/18 Updated: 06/Dec/22 Resolved: 02/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.7.3 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | MaxH, pm-1051-legacy-tickets | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
Some commands creates a temp collection locally and later renames them to the final collection. These commands will need special handling to register them into config.collections:
|
| Comments |
| Comment by Max Hirschhorn [ 02/Nov/22 ] |
|
There will be a separate project for having all collections be sharded upon creation with a single chunk range {_id: MinKey} to {_id: MaxKey}. |