[SERVER-59844] Use the currentOp server command in change_stream_update_lookup_read_concern.js Created: 09/Sep/21  Updated: 29/Oct/23  Resolved: 10/Sep/21

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

Type: Bug Priority: Major - P3
Reporter: Ruoxin Xu Assignee: Ruoxin Xu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 13

 Description   

After SERVER-47603, currentOp shell helper was rewritten to an equivalent aggregate command with an implicitly set "primaryPreferred" read preference, but the currentOp in this jstest should ignore any read preference set as the currentOp server command does.



 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 Githook User [ 09/Sep/21 ]

Author:

{'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}

Message: SERVER-59844 Use the currentOp server command in change_stream_update_lookup_read_concern.js
Branch: master
https://github.com/mongodb/mongo/commit/cc9d95cdff64e048d72b4894eb64f01e3c603514

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