-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
ALL
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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 this cache entry. The LRU mechanism will handle evicting this dead entry.
- related to
-
SERVER-130790 Handle bumping CollectionTag/index fingerprints if multikeyness flips due to document write
-
- Backlog
-