BugZero found this defect 2401 days ago.
All data on this page is proprietary to BugZero or gathered from public sources
No fixed releases provided.
This means we'll have to call listCollections twice on the primary shard if we want to avoid shardCollection being able to fail after creating the collection on the shard. We should avoid this because the user may change the options to shardCollection to try to fix their issue, and the new options may be incompatible with the options the collection was just created with. For example, if the first (failed) shardCollection attempt specified one shard key and passed the 'unique' option, and the second attempt specifies a different shard key, the second attempt will fail because a unique index was created on the shard with the first key. Depends on SERVER-29858, since we don't want to add new uses of DBClient in sharding, but ShardRemote does not have a way to iterate a cursor on shards.
email@example.com commented on Tue, 1 Aug 2017 14:56:12 +0000: Will be done as part of SERVER-29760.
Understand the cost to your business and how BugZero can help you reduce those costs.
Login to read and write comments.