Modularize index constraint violations checking into an independent action

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Constraint checking must be separated from finishing the building phase of an index. Separate function calls on the MultiIndexBlock (index builder).

      Simultaneous index builds on secondaries cannot proceed with constraint violations checking until signaled to do so by the primary. Secondaries should therefore be able to finish building the index itself (scanning, writing), and then at a later point in time perform the constraint violation checks.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: