[SERVER-63782] Avoid repeated copy of ViewsForDatabase in UncommittedCatalogUpdates Created: 17/Feb/22  Updated: 26/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: catalog, oldstorexemea, techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-57250 CollectionCatalog should handle and o... Closed
Assigned Teams:
Catalog and Routing
Participants:

 Description   

As a result of SERVER-57250, view DDL operations will atomically replace the ViewsForDatabase object. If two or more such operations happen in the same storage transaction, each will register a full copy of the ViewsForDatabase object with the UncommittedCatalogUpdates class. We could probably refactor this in such a way that if we already have a copy stored in UncommittedCatalogUpdates, we can modify it directly rather than creating an additional copy.


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