[SERVER-63000] createPredicatesOnBucketLevelField with $in should be treated like $or Created: 26/Jan/22 Updated: 29/Oct/23 Resolved: 27/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.3.0 |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Hana Pearlman | Assignee: | Hana Pearlman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | greenerbuild | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
It's possible that the children of an $in match expression cannot be translated to a predicate on a bucket-level field, e.g. when the children are object- or array-valued. In those cases, we should do what we do for the $or case: mark the entire $in as "always true", rather than inserting potentially null predicates as its translated children. |
| Comments |
| Comment by Githook User [ 27/Jan/22 ] |
|
Author: {'name': 'Hana Pearlman', 'email': 'hana.pearlman@mongodb.com', 'username': 'HanaPearlman'}Message: |