Use Case

As a write concern 0 user
I want the driver to set the fire-and-forget bit
So that the server handles the unacknowledged write as expected

See spec:
https://github.com/mongodb/specifications/blob/master/source/message/OP_MSG.rst#moretocome-on-requests

User Impact

• Has the potential to change the outcome of writes, operations that once would fail could now succeed.

Dependencies

• None

Unknowns

• Is this a breaking change?
• Has the Node driver ever set this flag under any circumstance?
• Impact on shell?

Acceptance Criteria

Implementation Requirements

• If the command being run has a writeConcern w setting of 0 set the moreToCome bit on the outgoing OP_MSG message.

Testing Requirements

• Integration:
  • Ensure that a multi: true update with a replacement-style document does not return a write error
• Unit:
  • Ensure moreToCome bit is set if there is an applied writeConcern to the command.

Documentation Requirements

• Update TSDoc over "w" settings to mention the side-effect of setting w:0 on the protocol message.

Follow Up Requirements

• None