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

Improve the inheritance rules for write concerns

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Native, Operations Layer
    • None

      Dan points out here that:

      Under this behavior, if the user overrides either w, j, or fsync, we will ignore the entire default write concern.
      
      For example if the collection has a writeConcern with w and j defined, and the user specifies a new value for w, our new writeConcern will only have w, not j.
      
      Is that expected behavior?
      
      Also, should the user be able to specify a new writeConcern value for wtimeout only?
      

      We should thoroughly refactor this inheritance logic, addressing all of his concerns.

            Assignee:
            Unassigned Unassigned
            Reporter:
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: