Duplicate read concern error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.5.0
    • Component/s: None
    • None
    • None
    • Dotnet Drivers
    • 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

      In some cases we send duplicate read concern to the server, due to the fact that it can be added both by:

      • Certain operations, for example in FindOperation
      • CommandUsingCommandMessageWireProtocol.

      CreateType0Section 

      Sending a duplicate read concern will return an error on the server. 
      We need to respect the default hierarchy of precedence for read/write concern as also explained in our docs.

      How to reproduce:

      • Create a collection with non-default read concern
      • Open a snapshot session
      • Execute a Find 

      This can happen also with transactions. 

            Assignee:
            Unassigned
            Reporter:
            Ferdinando Papale
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: