There are two constructors to CollectionImpl, one taking the whole metadata object from the DurableCatalog and one for just the CollectionOptions. Ideally it would be a nicer encapsulation if the metadata was read when creating the CollectionImpl but it is often needed before the CollectionImpl instance is created.
We should unify the interfaces and fix so all callsites creating collections can use the interface that provides the metadata.
- is related to
-
SERVER-56023 listCollections can return empty metadata for a collection which has been concurrently dropped
- Closed