[SERVER-64926] Allow calling moveRange with only max bound Created: 25/Mar/22  Updated: 29/Oct/23  Resolved: 03/Mar/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: Pierlauro Sciarelli Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-65013 Optional min bound for `moveRange` Closed
Documented
is documented by DOCS-15938 Investigate changes in SERVER-64926: ... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-03-06
Participants:

 Description   

SERVER-64148 introduced the possibility of invoking `moveRange` by specifying only the `min` bound. Purpose of this ticket is to allow specifying only the `max` bound, resulting in the index getting scanned backwards to find a suitable spit point.



 Comments   
Comment by Githook User [ 03/Mar/23 ]

Author:

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

Message: SERVER-64926 Allow calling moveRange with only max bound
Branch: master
https://github.com/mongodb/mongo/commit/a3489953893de85fa30c70e56cac65ffff5000ae

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