[SERVER-61395] clustered_util::matchesClusterKey should check for compound keys Created: 10/Nov/21 Updated: 29/Oct/23 Resolved: 15/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Josef Ahmad |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2021-11-15, Execution Team 2021-11-29 | ||||
| Participants: | |||||
| Linked BF Score: | 26 | ||||
| Description |
|
Right now, matchesClusterKey will return a false positive when provided with a compound index whose first field matches the cluster key Eg) clusterKey: {_id: 1}... |
| Comments |
| Comment by Githook User [ 15/Nov/21 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: |