Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-1899

Fix bulkWrite API's option resolutions and handling of ignoreUndefined

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Native, Operations Layer
    • Not Needed
    • 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?

      The bulkwrite API has a lot of problems with option resolution. Currently, the two issues we face are:

      1. BulkWrites can take some options either at construction (collection.initializeOrderedBulkWrite();) or at execution (bulkOp.execute(). The resolution of these options (which ones are given higher priority) are not consistent with our API overall, and are not clear to users.

      2. Certain options like ignoreUndefined can be specified in execute, but are needed for calculations beforehand. See NODE-1898.

      We should consider, at the next breaking version, refactoring the BulkWrite API to be more consistent.

            Assignee:
            Unassigned Unassigned
            Reporter:
            daniel.aprahamian@mongodb.com Daniel Aprahamian (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: