-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
This covers all code under the s/commands/query_cmd and s/query/planner folder., as well as any cluster command helpers called by that code. 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
-
- duplicates
-
SERVER-104020 Migrate scatterGatherVersionedTargetByRoutingTable functions to take in RoutingContext instead of CRI
-
- In Code Review
-
- is related to
-
SERVER-104020 Migrate scatterGatherVersionedTargetByRoutingTable functions to take in RoutingContext instead of CRI
-
- In Code Review
-
- 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
-
-
SERVER-103988 Change "RouteContext" to a more descriptive name
-
- Needs Scheduling
-