-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
This covers all code under the db/pipeline folder, particularly the process_interface classes. All routing operations performed here should use the RoutingContext to obtain routing tables instead of the CatalogCache. It should be passed down the call stack to cover the entire routing operation.
Existing behavior that propagates StaleConfigException or other errors up the call stack should be maintained.
- depends on
-
SERVER-102922 Provide a list of all direct CatalogCache accesses in the query layer
-
- Closed
-
-
SERVER-102923 Introduce the RoutingContext API
-
- Closed
-
- related to
-
SERVER-104395 Replace getCollectionRoutingInfoForTxnCmd with RoutingContext
-
- In Progress
-
-
SERVER-102931 Integrate CollectionIncarnationSnapshot with RoutingContext
-
- Needs Scheduling
-
-
SERVER-102934 Add comprehensive testing to ensure that the RoutingContext handles StaleConfigException correctly
-
- Needs Scheduling
-