[SERVER-62528] Add ability to run cursor establishment phase against mongot when a search pipeline is detected Created: 11/Jan/22  Updated: 03/Mar/22  Resolved: 03/Mar/22

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

Type: Task Priority: Major - P3
Reporter: Joe Kanaan Assignee: Ted Tuckman
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-62535 Add ability to return multiple cursor... Closed
Sprint: QO 2022-02-07, QO 2022-02-21, QO 2022-03-07
Participants:

 Comments   
Comment by Ted Tuckman [ 03/Mar/22 ]

This was done as part of SERVER-62535, so closing

Comment by Ted Tuckman [ 04/Feb/22 ]

Everything in the epic was marked as a blocker when joseph.kanaan filed them, I'm not sure what our process is. Happy to lower all the tickets if thats wrong.

I'll change the name to be more general.

Comment by David Storch [ 04/Feb/22 ]

ted.tuckman it's a mistake that this is marked "Blocker", right?

Also, in my mind it won't be the mongotRemote stage which is responsible for setting up the two cursors (search results and metadata). I imagine that this logic would live outside of any DocumentSource, similar to how exchange is implemented.

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