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

Don't send readConcern.afterClusterTime for writes outside of transaction

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: core
    • Labels:

      Description

      See https://github.com/mongodb-js/mongodb-core/blob/837f31276d77cea9838f1ad907dc63650a042200/lib/wireprotocol/command.js#L132

      In our command construction, we are automatically adding a readConcern.afterClusterTime to every command that has a session. The Causal Consistency spec only says to add afterClusterTime to read commands, and explicitly says to not add it to runCommand-like behavior.

      While this will likely not break anything in the server, it does cause some errors when attempting to comply with spec tests that assert whether or not a readConcern is present

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            daniel.aprahamian Daniel Aprahamian (Inactive)
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: