[SERVER-4827] interleaved cursor results may contain some matches from non sparse index and some from sparse index Created: 31/Jan/12  Updated: 16/Aug/12  Resolved: 01/Feb/12

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Aaron Staple Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Currently we have different matching semantics for sparse vs non sparse indexes (since sparse indexes don't contain documents lacking the indexed field, those are not returned). With cursor interleaving in the query optimizer, if two indexes are used and one is sparse while the other is not, some documents may be loaded from each index. The resulting matching semantics will not be the same as the current sparse or non sparse matching semantics.


Generated at Thu Feb 08 03:07:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.