-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
0
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The fix for SERVER-23229 is really to update the index to distinguish the two values. Until then a fix would come with performance ramifications. As a mitigation (and to help some of our test infrastructure), we could add a query knob to disable the covered index scans when they lead to incorrect behavior.
- is related to
-
SERVER-23229 Projection incorrectly returns null value instead of missing field to user if projection is covered
-
- Backlog
-
- related to
-
SERVER-82155 [CQF] Ensure we generate covered plans by default for fields which may be null
-
- Closed
-