Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Optimization
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The CollectionIncarnationSnapshot should be passed down the call stack so that it is accessible to later routing sub-operations that use the RoutingContext. For now, it should validate that the RoutingContext only requests namespaces that already exist in the CollectionIncarnationSnapshot.

depends on

SERVER-102930 Introduce the CollectionIncarnationSnapshot

In Code Review

SERVER-102923 Introduce the RoutingContext API

Closed

SERVER-102933 Acquire CollectionIncarnationSnapshot in top-level routing entrypoints in query code

Needs Scheduling

duplicates

SERVER-105861 Plug the CollectionIncarnationSnapshot in

Backlog

is related to

SERVER-102925 Replace direct CatalogCache accesses in the sharded aggregation code with the RoutingContext

Closed

SERVER-102926 Replace direct CatalogCache accesses in the sharded query command code with the RoutingContext

Closed

SERVER-102929 Replace direct CatalogCache accesses in MongoProcessInterface with the RoutingContext

Closed

related to

SERVER-107299 Complete TODO listed in SERVER-102931

Open

(2 is related to, 1 related to)

Assignee:: Unassigned
Reporter:: Lynne Wang
Participants:: Lynne Wang
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Mar 26 2025 06:10:30 PM UTC
Updated:: Jul 09 2025 07:36:51 AM UTC
Resolved:: Jul 08 2025 08:37:39 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates