[SERVER-63683] Explore a path to move the view catalog's persisted state away from being database oriented Created: 15/Feb/22  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: catalog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-63679 Dissociate the in-memory view catalog... Blocked
related to SERVER-63681 Explore elimination of the MODE_X col... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

The persisted view catalog per database is stored underĀ <db>.system.views.

  • The view catalog is split up across many persisted collections instead of stored in a single one
  • This is separate from our regular catalog information in the __mdb_catalog

ViewGraphs are created per database rather than as part of a global ViewGraph

  • A ViewGraph today can become invalidated and require reload (not sure how invalidation happens)
  • We'd have to support more fine-grained reloads/invalidations, or stop supporting invalidation of the view graph.

It would probably be wise to consider how we're going to handle materialized views, eventually, so we move non-materialized view handling in a direction that can also supports materialized views eventually.


Generated at Thu Feb 08 05:58:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.