[SERVER-18725] Use PlanExecutor::enqueue() in favor of PipelineProxyStage::pushBack() Created: 28/May/15  Updated: 01/Oct/15  Resolved: 01/Oct/15

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

Type: Improvement Priority: Minor - P4
Reporter: David Storch Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-17839 Remove PlanStage::isEOF Backlog
Duplicate
duplicates SERVER-16444 Avoid copying data out of WT buffers ... Closed
Related
is related to SERVER-17575 Handle BSONObj size limits for find/g... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

ebd449e59e6 under SERVER-17575 introduced a method PlanExecutor::enqueue(). If a client to the query system retrieves a result but then is unable to consume it, you can push the result document back onto the PlanExecutor's stream using enqueue().

The aggregation command currently has its own implementation for this inside the PipelineProxyStage. Since there is now a general mechanism, aggregation should move to using PlanExecutor::enqueue(). This will become easier after SERVER-17839 is implemented.



 Comments   
Comment by Max Hirschhorn [ 01/Oct/15 ]

Note that the _stash member of PipelineProxyStage cannot be removed until SERVER-17839 is done.

Comment by David Storch [ 01/Oct/15 ]

Fixed under SERVER-16444 in 764e0c4547. Closing as a duplicate.

Generated at Thu Feb 08 03:48:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.