Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- M2
- join-plan-cache

Assigned Teams:

Query Optimization
CAR Domain/s:
None

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

As stated in SPM-3143, multikeyness flips from a document write operation are not subject to the same strict transactional guarantees as DDL operations. This means that updating the necessary versions and fields due to such an operation will require careful synchronization.

is related to

SERVER-134942 Tripwire assertion 3994303 "$expr comparison predicates on multikey paths cannot use an index" index_bounds_builder/index_bounds_builder.cpp:1060 mongo::IndexBoundsBuilder::_translatePredicate

Backlog

SERVER-136939 Multikeyness change during planning but before plan cache insertion causes incorrect query results

Needs Scheduling

related to

SERVER-134800 Tripwire assertion Location12926305 Could not find index for INLJ collection reorder_joins.cpp:668:65:auto mongo::join_ordering::fromCachedJoinPlan

Closed

SERVER-129267 [Join Optimization] Ensure DDLs bump the current collectionVersion

Closed

Assignee:: Unassigned
Reporter:: Naafiyan Ahmed
Participants:: Naafiyan Ahmed
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Jul 07 2026 11:31:58 PM UTC
Updated:: Oct 13 2026 09:32:23 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty