Separate write conflict throwing library from write conflict handling library

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The write conflict retry header has a direct Locker dependency.

      Internal storage engine code should not require this dependency. Separate the libraries into what the storage engine needs (throwing code) from what higher-layers need (retrying code).

            Assignee:
            Unassigned
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: