[DOCS-15938] Investigate changes in SERVER-64926: Allow calling moveRange with only max bound Created: 03/Mar/23  Updated: 13/Nov/23  Resolved: 18/Jul/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Sarah Simpers
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-64926 Allow calling moveRange with only max... Closed
Participants:
Days since reply: 48 weeks, 5 days ago
Story Points: 2

 Description   
Original Downstream Change Summary

Made `max` field optional in the moveRange command. Now, the user can specify either: min only (as before), min + max (as before), or max only (new).
In the docs, we will need to change the moveRange command page to note that min is optional if max is specified and vice versa.
And add that if the user only specifies a max key, given a chunk C with the max bound `max`, the min key will be determined as
1. If the data size of the range between min(C) and max is less than the per-collection chunk size or the default chunk size, the chunk's min is selected as min = min(C)
2. otherwise key min > min(C) where min depends on the configured chunk size

Description of Linked Ticket

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.


Generated at Thu Feb 08 08:14:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.