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

XMLWordPrintableJSON

    • Not Needed
    • None
    • 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

      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

            Assignee:
            Unassigned
            Reporter:
            Daniel Aprahamian (Inactive)
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: