Don't report un-inserted duplicates for secondary indexes during initial sync

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • ALL
    • Storage NYC 2019-02-25
    • 50
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Divjot Arora (Inactive)
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: