SERVER-56002 added a cached version of the index metadata stored in the DurableCatalog in the Collection instance. As the IndexCatalogEntry is just a member of the Collection it should be consistent to use.
We can avoid having multiple caches of the same values that need to be kept in sync.
- is related to
-
SERVER-56002 listIndexes can read partial state from renameCollection
- Closed
-
SERVER-56023 listCollections can return empty metadata for a collection which has been concurrently dropped
- Closed
- related to
-
SERVER-56877 insert operations may fail to set index to multikey after aborted multikey catalog update
- Closed
-
SERVER-57775 collection metadata for multikey not removed after WriteConflictException from durable catalog update
- Closed
-
SERVER-57178 add regression test for multikey compound index
- Closed
-
SERVER-57268 add multikey query to validate_multikey_restart.js
- Closed
-
SERVER-57385 support looking up multikey state by index offset in Collection interface
- Closed