legacy update path cleanup

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Write Ops
    • None
    • Query Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There are a few improvements to the update path for legacy writes (see receivedUpdate in instance.cpp) which we should consider.

      1. There is a separate WriteConflictException retry loop for the collection creation case, i.e. upsert into an empty collection. We should be able to consolidate this into a single retry loop.
      2. The catch block for WriteConflictException logs and then re-throws the exception if it is a multi-update. The UpdateStage, however, should be responsible for catching WriteConflictException in the multi-update case.

              Assignee:
              [DO NOT USE] Backlog - Query Execution
              Reporter:
              David Storch
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: