[SERVER-38695] Make QuerySolutionNode subclasses for projection fast-paths Created: 18/Dec/18  Updated: 29/Oct/23  Resolved: 29/Jan/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.1.8

Type: Improvement Priority: Major - P3
Reporter: Jacob Evans Assignee: Jacob Evans
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-37831 Optionally decouple WorkingSetMember ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2019-01-14, Query 2019-01-28, Query 2019-02-11
Participants:

 Description   

In SERVER-37831 find projection execution has been separated into three classes: one with the full implementation and two with different fast paths. We should create corresponding QuerySolutionNode subclasses because we want a one-to-one correspondence between PlanStages subclesses and these. Intuitively we want the planner to have direct knowledge of which implementation it is choosing.



 Comments   
Comment by Githook User [ 30/Jan/19 ]

Author:

{'email': 'jacob.evans@10gen.com', 'name': 'Jacob Evans'}

Message: SERVER-38695 Make QuerySolutionNode subclasses for projection fast-paths
Branch: master
https://github.com/mongodb/mongo/commit/41557fac170a905cb7b0cca7564e4c0ec48bbefd

Generated at Thu Feb 08 04:49:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.