[SERVER-39563] Don't report un-inserted duplicates for secondary indexes during initial sync Created: 13/Feb/19 Updated: 13/Feb/19 Resolved: 13/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Divjot Arora (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Storage NYC 2019-02-25 | ||||
| Participants: | |||||
| Linked BF Score: | 50 | ||||
| Description |
|
The code here assumes that if dupRecords is passed, then the caller wants a set of un-inserted duplicates. If dupRecords is passed, the uniqueness of the index informs whether or not to ignore duplicates, overriding any previous call ignoreUniqueConstraint(). In this case x_1 is unique, so it will not ignore duplicates. In this case, the caller doesn't even want this set of un-inserted duplicate records. We should just not pass dupRecords to dumpInsertsFromBulk for secondary indexes, so that all duplicates get inserted and ignored, as expected. |
| Comments |
| Comment by Louis Williams [ 13/Feb/19 ] |
|
It turns out this is actually not a problem. Closing |