[SERVER-68935] Ban PathIdentity in Filter context Created: 18/Aug/22 Updated: 29/Oct/23 Resolved: 17/Jan/23 |
|
| 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: | Ted Tuckman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QO 2023-02-06 |
| Participants: |
| Description |
|
We should ban the use of PathIdentity under EvalFilter. This will require asserting here, but it may also require changes in the optimization code to ensure PathId cannot be generated under EvalFilter by some rewrite |
| Comments |
| Comment by Githook User [ 17/Jan/23 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |