[SERVER-35974] Create a DocumentSourceExchangeConsumer Created: 05/Jul/18  Updated: 06/Dec/22  Resolved: 13/Jul/18

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

Type: Task Priority: Major - P3
Reporter: Kyle Suarez Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-35905 Plug pieces together to perform a dis... Closed
Assigned Teams:
Query
Participants:

 Description   

To complement the DocumentSourceExchangeProducer being written in SERVER-35894, we need a DocumentSourceExchangeConsumer that will house the logic for merging the results of multiple cursors into one stream. The idea is to use the AsyncResultsMerger to gather results.



 Comments   
Comment by Kyle Suarez [ 05/Jul/18 ]

david.storch mentioned that we already have a DocumentSourceMergeCursors; we should first investigate if this thing can satisfy our needs for the exchange consumer side, perhaps by subclassing if necessary.

Comment by Esha Maharishi (Inactive) [ 05/Jul/18 ]

As part of this, maybe check if the ClusterClientCursor's interface would be better than using the ARM's interface directly.

For example, ClusterClientCursor's interface might be better if you want to use ClusterClientCursorParams.

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