[DOCS-14742] Clarify null vs missing behavior in group _id Created: 17/Aug/21 Updated: 30/Oct/23 Resolved: 18/May/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Patrick Meredith | Assignee: | Backlog - Query Optimization |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 37 weeks, 6 days ago |
| Description |
|
In some situations null and missing are considered equivalent for the group key, in other places they are considered as distinct. Since it is likely impossible that we can change this behavior since it is user facing, we should document it for clarity.
|
| Comments |
| Comment by Sarah Olson [ 18/May/23 ] |
|
Closing this ticket as WON'T FIX because it is relatively old and it appears that we were unable to reach consensus on whether this is intended behavior for documentation or a bug for the engineering team to address. Please don't hesitate to reach out if you have concerns or would like to reopen this ticket. |
| Comment by Ryan Chipman [ 19/Aug/21 ] |
This assumes that this is intended behavior, and not a bug. I'd be curious to understand why this is considered intended behavior that should be documented as opposed to a bug – at first glance, this looks like a bug to me. |
| Comment by Eric Sedor [ 17/Aug/21 ] |
|
Agreed Patrick; I think this belongs in https://docs.mongodb.com/manual/reference/operator/aggregation/group/#considerations. I'm moving this to the DOCS project |