[SERVER-73234] Fix TODO comment with wrong ticket ID Created: 24/Jan/23  Updated: 29/Oct/23  Resolved: 08/Feb/23

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

Type: Task Priority: Major - P3
Reporter: PM Bot Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: autogen-todo, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-7279 Windows: Test TCMalloc performance an... Closed
is related to SERVER-70795 Modify rename to update the index cat... Closed
is related to SERVER-72796 Remove pre 6.3 compatible code once 7... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-02-06
Participants:

 Description   

SERVER-70795 added a wrong ticket ID in the code. Fix the comment.



 Comments   
Comment by Githook User [ 07/Feb/23 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-73234 Fix wrong TODO comment pointing to a wrong jira ticket
Branch: master
https://github.com/mongodb/mongo/commit/4468cd7473aaeecdd4c621aa7a75d94c581d3d9e

Comment by Max Hirschhorn [ 24/Jan/23 ]

It looks like https://github.com/mongodb/mongo/blob/e4fff3e1fe7b31b25cedde7b05205325b47b4a7d/src/mongo/db/s/sharding_ddl_coordinator_service.cpp#L80 may have intended to be a "TODO SERVER-72796" comment instead. CC marcos.grillo@mongodb.com

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