Add Mongo prefix to exception class names that don't already have it

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 1.10
    • Affects Version/s: 1.9.2
    • Component/s: Error Handling
    • None
    • None
    • Minor Change
    • None
    • None
    • None
    • None
    • None
    • None

      In 2.0 we are refactoring the exception class hierarchy, as well as adding the Mongo prefix to the few exception class names that didn't already have it.

      To prepare the path for migration to 2.0, in 1.10 we will deprecate the 3 exception classes that don't already have a Mongo prefix:

      • BulkWriteException
      • ExecutionTimeoutException
      • WriteConcernException

      We will introduce new exceptions with the Mongo prefix, and arrange the class hierarchy so that your existing code will catch either one (for example, if we make the new MongoBulkWriteException a subclass of BulkWriteException, existing code that catches a BulkWriteException will continue to catch a MongoBulkWriteException).

              Assignee:
              Robert Stam
              Reporter:
              Robert Stam
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: