[SERVER-37544] Allow moveChunk command for unsharded collections Created: 10/Oct/18  Updated: 06/Dec/22  Resolved: 02/Nov/22

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

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Do Votes: 0
Labels: MaxH, pm-1051-legacy-tickets
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Sprint: Sharding 2018-11-19
Participants:

 Description   

Enable the moveChunk command for chunks of non sharded collections.

Steps:
1. Set the UUID in the collection entry in config.collections when creating the collection and inserting into config.collections.

Testing:
1. Test moveChunk on a non-sharded collection and pass the dummy shard key {_id : 1} as key to "find" in the moveChunk parameters.

  1. Do this for both an empty and non-emtpy colleciton.
    2. Test moveChunk on a non-empty non-sharded collection and pass the [min, max] as the bounds to the moveChunk command.


 Comments   
Comment by Max Hirschhorn [ 02/Nov/22 ]

There will be a separate project for having all collections be sharded upon creation with a single chunk range {_id: MinKey} to {_id: MaxKey}.

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