Consolidate WriteConflictException and related exceptions into an error category

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Programmability
    • SP Prioritized List
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The code base relies heavily on WriteConflictException, TemporarilyUnavailableException and TransactionTooLargeForCacheException deriving from DBException. Defining an error category for these exceptions today would cause those exceptions to derive from AssertionException instead. This is problematic because locations that catch AssertionExceptions will also start catching these exceptions; this is not desirable as it'll prevent these exceptions from bubbling up to their intended handler (e.g., writeConflictRetry).

            Assignee:
            Unassigned
            Reporter:
            Josef Ahmad
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: