[SERVER-63253] Ensure CollectionUUIDMismatch error from find command does not omit the actual collection even if unsharded Created: 03/Feb/22 Updated: 29/Oct/23 Resolved: 15/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-02-07, Execution Team 2022-02-21 |
| Participants: |
| Description |
|
Say coll1 (with uuid1) is sharded and coll2 (with uuid2) is unsharded, and the command {find: coll1, filter: ..., collectionUUID: uuid2} is issued where the filter causes the find to target only the non-primary shard. Then the returned CollectionUUIDMismatch will erroneously not contain coll2, because it only exists on the primary shard. We should make sure that regardless of which shards are targeted and no matter whether collections are sharded are unsharded, the CollectionUUIDMismatch contains all of the information that it should. |
| Comments |
| Comment by Githook User [ 15/Feb/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |