[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:
Duplicate
is duplicated by SERVER-42432 Use ProjectionAST in query planner in... Closed
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: SERVER-42422 replace ParsedProjection with ProjectionAST in the query planner
Branch: master
https://github.com/mongodb/mongo/commit/dafd5d069c74b5ca92cf1ccba7a6a8386a5abe52

Comment by Ian Boros [ 25/Jul/19 ]

Talk to me before starting this

Generated at Thu Feb 08 05:00:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.