Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.1.0-rc0, 9.1.0-rc1025
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
Sprint:
Storage Execution 2026-11-09
CAR Domain/s:
None

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

With SERVER-134912, PDIB piggybacks multikey updates in "i" side writes, rather than having them in their own "m" entries. We should consider making it so that all hybrid builds (PDIB or not) write multikey updates into dedicated "m" entries. This would allow us to avoid much of the complexity of SERVER-134912 where we have to have special handling for the case where an update operation changes multikey while not contributing any new keys.

depends on

SERVER-135369 Add multikey side write op type

Closed

is depended on by

SERVER-138614 Remove handling of multikey piggypacked on insert side write entries in index builds

Open

SERVER-138694 Add metric for index build multikey side writes

Closed

SERVER-135262 A sparse index can be considered multikey even if the would-be multikey document generates no keys

Closed

related to

SERVER-138833 Complete TODO listed in SERVER-135300

Needs Scheduling

Assignee:: Gregory Noma
Reporter:: Gregory Noma
Participants:: Gregory Noma
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Sep 19 2026 01:26:14 AM UTC
Updated:: Nov 06 2026 04:32:37 AM UTC
Resolved:: Nov 05 2026 05:37:00 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty