Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Minor Change
-
ALL
-
v4.2, v4.0, v3.6
-
Sharding 2018-09-24, Sharding 2018-10-08, Sharding 2018-10-22, Sharding 2018-12-03, Sharding 2018-12-17, Sharding 2018-12-31, Sharding 2019-01-14, Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25, Sharding 2019-03-11, Sharding 2019-03-25, Sharding 2019-09-09
Description
In storeClonedLocs(), we use nsd->findIndexByPrefix(), in removeRange() we use nsd->findIndexByKeyPattern(). This may be a problem if the user has multiple indexes prefixed by the shard key and some of the indexes are sparse.
Attachments
Issue Links
- is duplicated by
-
SERVER-18226 shardCollection command can orphan documents that are missing shard key if sparse index present
-
- Closed
-
- related to
-
SERVER-18226 shardCollection command can orphan documents that are missing shard key if sparse index present
-
- Closed
-