[SERVER-85229] The same distinct command, the result sometimes contains null and sometimes does not Created: 16/Jan/24 Updated: 23/Jan/24 Resolved: 23/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.8, 6.0.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | 志刚 柴 | Assignee: | Backlog - Query Execution |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | Bug | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
version:6.0.12 4.2.8 db.t1.insert({id:1})
— There are no nulls in the result set
– After creating the index, there are nulls in the result set
After adding the index, null values appeared in the result set, causing the application processing logic to change. I would like to ask if this is a bug. |
| Comments |
| Comment by Kyle Suarez [ 23/Jan/24 ] | |||||||||
|
Hello chaigang@126.com, Thank you for your report. This is a known issue and is tracked in SERVER-14832. Any fixes will be tracked in that ticket. | |||||||||
| Comment by Chris Kelly [ 17/Jan/24 ] | |||||||||
|
Hi chaigang@126.com, Thanks for your report. Some initial comments:
I will forward this to the relevant team to confirm whether this is intended behavior. | |||||||||
| Comment by 志刚 柴 [ 16/Jan/24 ] | |||||||||
|
db.t1.find() { “_id” : ObjectId(“65a62118842d8bddd7ef9699”), “id” : 1 } { “_id” : ObjectId(“65a62119842d8bddd7ef969a”), “id” : 2 } { “_id” : ObjectId(“65a6211c842d8bddd7ef969b”) } { “_id” : ObjectId(“65a6211f842d8bddd7ef969c”), “id” : 2 } |