[SERVER-48478] Create a PlanExecutor implementation for executing a Pipeline Created: 28/May/20  Updated: 29/Oct/23  Resolved: 24/Jul/20

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

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: David Storch
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-49808 Report execution stats for logging/pr... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Query 2020-07-13, Query 2020-07-27
Participants:

 Description   

As part of adding the slot-based execution (SBE) engine, we will have multiple implementations of the PlanExecutor interface: one for the "classic" execution engine and another for SBE. This will require us to convert PlanExecutor into a clean interface that can abstract over multiple execution engines (see SERVER-48477). Therefore, it would make sense to have a third implementation of PlanExecutor which is used for executing Pipelines of DocumentSources. This will allow us to get rid of the PipelineProxyStage which currently sits between PlanExecutor and the Pipeline. Using PipelineProxyStage when SBE is enabled is particularly undesirable because it causes the runtime execution plan tree to involve both SBE PlanStages and classic PlanStages.



 Comments   
Comment by Githook User [ 24/Jul/20 ]

Author:

{'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}

Message: SERVER-48478 Replace PipelineProxyStage with PlanExecutorPipeline
Branch: master
https://github.com/mongodb/mongo/commit/b4b35f9cc69412611a198642333bf40daa5ba58c

Comment by Githook User [ 24/Jul/20 ]

Author:

{'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}

Message: SERVER-48478 Use PlanExecutorPipeline in mqlrun
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/3c4424e7e5a2c3bae81b5929a939a8712d9e5998

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