[SERVER-72987] analyzeShardKey misclassifies range queries in hashed sharding Created: 18/Jan/23 Updated: 29/Oct/23 Resolved: 21/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding NYC 2023-01-23 |
| Participants: |
| Description |
|
The analyzeShardKey {Read,Write}DistributionCalculator currently classifies all shard key range queries as targeting a variable number of shards (i.e. not necessary all shards). The classification isn't correct in the case of hashed sharding, since in that case range queries target all shards. |
| Comments |
| Comment by Githook User [ 21/Jan/23 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |