[COMPASS-6043] Investigate changes in SERVER-67127: Delete shell logic to fall back to currentOp command rather than $currentOp stage Created: 22/Aug/22  Updated: 23/Aug/22  Resolved: 23/Aug/22

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-67127 Delete shell logic to fall back to cu... Closed
Documentation Changes: Not Needed

 Description   
Original Downstream Change Summary

This ticket removes support for the `db.currentOP()` helper from the legacy shell. This was an alias for `db.currentOp()` that appeared to be unused in the server code base. Uses of `db.currentOP()` outside of the server code base which could run inside the 6.1+ legacy mongo shell should be changed to `db.currentOp()`.

Description of Linked Ticket

The shell's currentOp() helper has some logic to fallback to the old currentOp command rather than the $currentOp aggregation stage when it is connected to the Atlas Proxy:

https://github.com/mongodb/mongo/blob/3a49875934cfd7e70d789b4ad7093286d189acc9/src/mongo/shell/db.js#L810-L815

It's possible that this fallback logic is safe to delete, though we should check with the knowledgeable folks on the Cloud team. My thinking is that since new versions of the shell are no longer shipped to users, this fallback logic should be ok to get rid of. We don't need it in the server's testing environment (because we don't test the Atlas Proxy in this environment), and the current remaining purpose of the mongo shell is to act as the testing harness for the server.


Generated at Wed Feb 07 22:41:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.