add do_not_shard_destination option #866
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Firstly thanks a lot for the useful tool you built and shared with the world 🙏
We had a use case where we intended to move a 300GB sharded collection hosted on Mongo Atlas to another regular non-sharded replicaset. Due to the fact that the collection on each shard accidentally had different UUIDs (strange technical quirk of MongoDB) reducing shard number to 0 and then moving it was not possible.
We leveraged MongoShake to move all our data. We slightly modified the source code with this flag to skip over the step where the tool shards the destination database/collection to match the configuration of the source.
I thought other people may find it useful too.