[SERVER-55223] Do not use KeyString for metadata comparisons in BucketCatalog Created: 16/Mar/21 Updated: 17/Mar/21 Resolved: 17/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Dan Larkin-York |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Execution Team 2021-03-22 |
| Participants: |
| Description |
|
Currently the BucketCatalog uses KeyString to facilitate metadata comparisons in the BucketCatalog. This lets numbers of different types compare equal when they shouldn't for this purpose. Instead, we should simply store a field-sorted object and then do a binary comparison over the object. |
| Comments |
| Comment by Githook User [ 17/Mar/21 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |