[COMPASS-6730] Investigate changes in PM-1966: Track views in the catalog Created: 18/Apr/23 Updated: 08/Jan/24 |
|
| Status: | Waiting (Blocked) |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Investigation | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Epic Link: | COMPASS-7048 | ||||
| Description |
|
Original Downstream Change Summary Backup will be impacted Description of Linked TicketEpic Summary SummaryMove tracking of views from the primary shard for a database, to the catalog, and make view definitions available on mongos MotivationThe status quo, where views are tracked on the primary shard for their database, has a few downsides:
Moving view definitions will solve those problems, improving performance, ability to perform query planning and removing a barrier to getting rid of the notion of primary shards (and in turn removing a barrier to removing the movePrimary command) Cast of Characters
DocumentationScope Document |
| Comments |
| Comment by PM Bot [ 04/Jan/24 ] |
|
Fix Version updated for upstream PM-1966: |