[SERVER-61333] The check to reject a snapshot read on a sharded collection via the "distinct" command should happen on mongod not mongos Created: 08/Nov/21 Updated: 29/Oct/23 Resolved: 08/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Kyle Suarez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QE 2021-12-13, QE 2021-12-27, QE 2022-01-10, QE 2022-03-07, QE 2022-03-21, QE 2022-01-24 |
| Participants: |
| Description |
|
This check can incorrectly reject a distinct command on an unsharded collection if there was a sharded collection that was dropped and recreated as unsharded. The check should instead be done on the shard using the shard's filtering metadata. |
| Comments |
| Comment by Githook User [ 08/Mar/22 ] |
|
Author: {'name': 'Kyle Suarez', 'email': 'kyle.suarez@mongodb.com', 'username': 'ksuarz'}Message: |
| Comment by Kaloian Manassiev [ 12/Nov/21 ] |
|
Assigning this to QE as we think they own the distinct command |