[SERVER-17457] Inclusion of "null" in "distinct" result depends on existence of index Created: 04/Mar/15 Updated: 04/Mar/15 Resolved: 04/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.6.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Yonatan Most | Assignee: | Unassigned |
| 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 calling distinct on a field which is missing from some of the records, the result either includes or does not include null, depending on whether there is an index in that field. |
| Comments |
| Comment by J Rassi [ 04/Mar/15 ] |
|
Hi, Thanks for the report. This is a known issue, described in SERVER-14832. I'm resolving this ticket as duplicate. Feel free to add yourself as a watcher to SERVER-14832 for updates. ~ Jason Rassi |