[SERVER-12019] Remove "lockType" from commands "help" output Created: 09/Dec/13  Updated: 14/Mar/17  Resolved: 13/Sep/16

Status: Closed
Project: Core Server
Component/s: Internal Code, Usability
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Spencer Brody (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-9575 Docs for SERVER-12019: Remove "lockTy... Closed
Duplicate
duplicates SERVER-11834 listCommands show write commands not ... Closed
Related
related to SERVER-11492 Upserts to config servers incorrectly... Closed
related to SERVER-11834 listCommands show write commands not ... Closed
Backwards Compatibility: Minor Change
Participants:

 Description   

Every command in the system can be run with the argument "help":1 to get help information about that command. The information returned contains a "lockType" field intended to indicate if that command takes a read or write lock, however that information comes from the locktype() method on every Command object, which is not accurate for most commands anymore as most commands now handle their own locking internally. We should remove this misleading and outdated field from the "help" output of all commands (or make it accurate for all commands, but that seems difficult to do).



 Comments   
Comment by Andy Schwerin [ 13/Sep/16 ]

This was fixed in SERVER-11834, for 2.5.5.

Comment by Andy Schwerin [ 11/Jun/15 ]

Scheduling for 3.3, since SyncClusterCollection is scheduled to be removed from the codebase in that release.

Comment by Spencer Brody (Inactive) [ 09/Dec/13 ]

Unfortunately this field is still relied upon in some outdated mongos code used for running commands on config servers, see the SyncClusterConnection::_lockType() method.

Generated at Thu Feb 08 03:27:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.