[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: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Participants: | |||||||||
| Description |
|
To complement the DocumentSourceExchangeProducer being written in |
| 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. |