[SERVER-64081] Update scanIndexForDuplicates to handle clustered index keys Created: 01/Mar/22 Updated: 03/Mar/22 Resolved: 03/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Shin Yee Tan | Assignee: | Shin Yee Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Execution Team 2022-03-07 |
| Participants: |
| Description |
|
Having clustered collections will use object id as record id. When comparing keystrings in scanIndexForDuplicates, we cannot assume that RecordId will be a long. We will need to update the comparison to something like this. Remove TODO in buildscripts/resmokeconfig/suites/clustered_collection_passthrough.yml to include collmod_convert_to_unique_violations_size_limit.js in the clustered collection passthrough. |
| Comments |
| Comment by Githook User [ 03/Mar/22 ] |
|
Author: {'name': 'Shin Yee Tan', 'email': 'shinyee.tan@mongodb.com', 'username': 'shinyeet'}Message: |