[SERVER-57462] Modernize shell support for exhaust queries to use OP_MSG instead of OP_QUERY Created: 04/Jun/21  Updated: 29/Oct/23  Resolved: 15/Jul/21

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

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: Yoon Soo Kim
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
Related
Backwards Compatibility: Minor Change
Sprint: Query Execution 2021-06-14, Query Execution 2021-06-28, Query Execution 2021-07-12, Query Execution 2021-07-26
Participants:

 Description   

This must be completed prior to removing support for OP_QUERY/OP_GET_MORE from the server.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Yoon Soo Kim [ 02/Jul/21 ]

Investigating how to implement exhaust support using OP_MSG in shell. There are two main alternatives.

  1. To use runCommand in query.js.
  2. To use dbclient.find() native implementation and force it to follow command path.
Generated at Thu Feb 08 05:41:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.