SERVER-136939Backlog

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

If an index becomes multikey during the planning of a query which has a stale snapshot of the non-multikey index, that query can activate its plan in the plan cache. At least in the repro attached, this results in missing/incorrect query results since we applied optimizations based on the non-multikeyness. One idea for the fix is to encode multikeyness of the index(es) when creating and inserting the plan cache entry. If multikeyness changes, then future queries of the same shape will not hit

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification
ca-candidateqo-triage-week