Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Won't Do
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Sprint:
CAR Team 2026-06-22, CAR Team 2026-07-06
CAR Domain/s:
None

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

The AsyncRequestSender::Reponse should contain a shardHandle if shard resolution completed. Callers now need to use the shardId if they are reporting information to the user or the uuid if they are doing something internally. We should update callers to do this, and provide helper functions to handle the error case in which the shardHandle is not necessarily populated.

depends on

SERVER-127947 Update AsyncRequestsSender to handle ShardRefs and ShardHandles

Closed

related to

SERVER-128701 Integrate the use of ShardRef into createDatabase

Open

SERVER-130277 Complete TODO listed in SERVER-128424

Needs Scheduling

Assignee:: Paolo Polato
Reporter:: Allison Easton
Participants:: Allison Easton, Paolo Polato
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Jun 08 2026 06:05:29 AM UTC
Updated:: Jul 01 2026 04:28:23 AM UTC
Resolved:: Jun 30 2026 03:30:07 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates