[SERVER-78695] Introduce a setClusterParameterCommand base class Created: 06/Jul/23  Updated: 20/Nov/23  Resolved: 20/Nov/23

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

Type: Improvement Priority: Major - P3
Reporter: Denis Grebennicov Assignee: Backlog - Query Execution
Resolution: Won't Fix Votes: 1
Labels: new-eng, tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-77463 Implement setQuerySettings command Closed
Assigned Teams:
Query Execution
Participants:

 Description   

As part of SERVER-77464 setQuerySettings command is calling setClusterParameter command on itself for further processing.

In order to avoid the setClusterParameter command to go through the DBDirectClient, a weak function was introduced that corresponds to the implementation of the setClusterParameter command invocation. This weak function is registered for both mongos and mongod implementations.

Since setClusterParameterCommand classes (for both mongos and mongod implementations) are relatively same and only differentiate with the invocation body, the idea behind this is ticket is to refactor it by introducing a new base class and in the derived classes just override the command invocation with the weak function call.

charlie.swanson@mongodb.com proposed this as part of the code review in this comment.


Generated at Thu Feb 08 06:39:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.