Collection.BulkWrite should handle ConnectionException

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Unknown
    • 4.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Dotnet Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      If there is ConnectionException happening while Collection.BulkWrite current version throw ConnectionException that makes no way to find what part of the BulkWrite was already processed by server. Driver should wrap the connection exception into BulkWriteException.

       

      Upskip the following unified tests once the bug is fixed: 

      retriableWrites/bulkWrite.json:Second updateOne is never committed

      retriableWrites/bulkWrite.json:Third updateOne is never committed

            Assignee:
            Oleksandr Poliakov
            Reporter:
            Oleksandr Poliakov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: