[SERVER-64587] Fail $lookup when undefined is a value from the local side Created: 16/Mar/22 Updated: 01/Apr/22 Resolved: 01/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mihai Andrei | Assignee: | Mihai Andrei |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | QE 2022-04-04 |
| Participants: |
| Description |
|
The following test case succeeds when it should fail. This ticket tracks the work to either fail $lookup in SBE when undefined is seen on the local side, or close the issue as 'won't fix' if we decide that we don't care about this case. |
| Comments |
| Comment by Irina Yatsenko (Inactive) [ 31/Mar/22 ] |
|
As far as product behaviour is concerned this ticket is WF (in SBE we will generate no matches for "undefined" in local), but similarly to https://jira.mongodb.org/browse/SERVER-64586 the difference between classic and SBE is likely to trip the fuzzers. |
| Comment by Ethan Zhang (Inactive) [ 29/Mar/22 ] |
|
Do we still care given that we don't plan to match behavior for `undefined`? Can we close this ticket as a Won't Fix? Maybe need to update the test case? mihai.andrei |