[SERVER-85298] distinct command with a winning plan of DISTINCT_SCAN returns null values, whereas COLLSCAN does not Created: 17/Jan/24 Updated: 24/Jan/24 Resolved: 24/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alex Bevilacqua | Assignee: | Chris Kelly |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: |
|
||||||||
| Participants: | |||||||||
| Description |
|
When executing a distinct command to identify distinct values within a collection, if the winning plan is a COLLSCAN the result set will exclude null values. If the winning plan is an IXSCAN (or a PROJECTION_COVERED/DISTINCT_SCAN) the result set will include the null values. I'm assuming this is by design, so if that's the case perhaps there's a documentation gap here. |
| Comments |
| Comment by Chris Kelly [ 24/Jan/24 ] |
|
This looks like a duplicate of |