[SERVER-86294] Use alternate feature flag to gate code that is post 8.0 Created: 06/Feb/24 Updated: 07/Feb/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | PM-3364-Milestone-4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: |
| Description |
|
The current plan for PM-3364 is to lazily track unsharded collections in order to move them using moveCollection for 8.0, then, in a post-8.0 world, we would fully track all unsharded collections. This means that there is code that we've already develop for this project (like for example, registering collections automatically on creation) that will not be activated for 8.0. This code will continue to be behind the current featureFlagTrackUnshardedCollectionsOnShardingCatalog. All the code that is necessary for 8.0 will be gated by a different feature flag instead. |