-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
Execution Team 2021-12-27, Execution Team 2022-01-10
-
145
This code does DatabaseHolder::getViewCatalog()->resolveView without checking that getViewCatalog doesn't return a nullptr. It makes this assumption because the code is gated by an autoGet->getView check.
Two solution here.
1) Aggregation can error when it finds the ViewCatalog no longer exists. (I rather like the simplicity). This means the collection didn't exist when the command started, and then the view went away somehow during the command. Aggregate is just about to drop locks anyway, which means anything can happen after view resolution
2) Lock-free operations must support ViewCatalog::resolveView with the same ViewCatalog used to fetch the view – likely save the ViewCatalog shared_ptr on the AutoGet*LockFree, if we find a view.
- is related to
-
SERVER-63684 Rollback SERVER-62101's work now that the view catalog is part of the collection catalog
- Closed