[SERVER-70812] Make find and agg translation for match expressions consistent Created: 24/Oct/22 Updated: 29/Oct/23 Resolved: 02/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Hana Pearlman | Assignee: | Ben Shteinfeld |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QO 2022-11-28, QO 2022-12-12 |
| Participants: |
| Description |
|
In the translation code for DocumentSourceMatch, we translate the match expression. Then, if the resulting ABT has a top-level composition, we flatten it into a chain of separate FilterNodes. In the find path, we don't do this second flattening step. This seems problematic. We probably want the ABTs for match expressions generated by the find path and agg path to be consistent. |
| Comments |
| Comment by Githook User [ 02/Dec/22 ] |
|
Author: {'name': 'Ben Shteinfeld', 'email': 'ben.shteinfeld@mongodb.com', 'username': 'bshteinfeld'}Message: |