[SERVER-77166] Consider getting rid of the `shouldMigrate` split reply field Created: 16/May/23  Updated: 31/Oct/23  Resolved: 31/Oct/23

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

Type: Task Priority: Minor - P4
Reporter: Pierlauro Sciarelli Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: car-qw, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-10-30, CAR Team 2023-11-13
Participants:
Story Points: 1

 Description   

When a split is performed on a chunk containing the shard key's lower/upper bound, the shouldMigrate field is appended to the command's reply.

Since the field was only internally used for top chunk optimization (gone away starting from v6.0.3) and has never been publicly documented, the proposal for this ticket is to simply get rid of such unused/misleading parameter.



 Comments   
Comment by Githook User [ 31/Oct/23 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-77166 Consider getting rid of the `shouldMigrate` split reply field
Branch: master
https://github.com/mongodb/mongo/commit/8ec39f47140c8d97a6f64bf8ec5d5402437bb7b9

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