[SERVER-42422] Implement dependency analysis on ProjectionAST Created: 25/Jul/19 Updated: 29/Oct/23 Resolved: 25/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Ian Boros |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Query 2019-09-09, Query 2019-09-23, Query 2019-10-07 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently the query system uses parsed_projection during planning to determine information about whether a query needs to be covered, and which metadata needs to be provided, etc. We will re-implement this logic on ProjectionAST. To start, this is the interface we should implement so that ProjectionAST can be used as a drop-in for parsed_projection. |
| Comments |
| Comment by Githook User [ 25/Sep/19 ] |
|
Author: {'username': 'puppyofkosh', 'email': 'ian.boros@mongodb.com', 'name': 'Ian Boros'}Message: |
| Comment by Ian Boros [ 25/Jul/19 ] |
|
Talk to me before starting this |