[SERVER-64368] Fix Incorrect Field Names In ShardingDataTransformMetrics Created: 09/Mar/22  Updated: 29/Oct/23  Resolved: 30/Mar/22

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

Type: Bug Priority: Major - P3
Reporter: Brett Nawrocki Assignee: Brett Nawrocki
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding NYC 2022-04-04
Participants:
Story Points: 1

 Description   

Some fields are being reported with the incorrect name in currentOp and serverStatus. These are as follows:

CurrentOp

Expected: "op", Actual: "command"
Expected: "originatingCommand", Actual: "originalCommand"

ServerStatus

Expected: "documentsProcessed", Actual: "documentsCopied"
Expected "bytesWritten", Actual: "bytesCopied"



 Comments   
Comment by Githook User [ 28/Mar/22 ]

Author:

{'name': 'Brett Nawrocki', 'email': 'brett.nawrocki@mongodb.com', 'username': 'brettnawrocki'}

Message: SERVER-64368 Fix incorrect field names in ShardingDataTransformMetrics
Branch: master
https://github.com/mongodb/mongo/commit/52b265a51ec234d493b0349a9654cb612eae00c0

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