Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13945

Clarify the purpose/usage of read write concern for user collections in "local" database.

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: manual, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      2
    • Sprint:
      ServerDocs2020: Oct27 - Nov3, ServerDocs2020: Nov3 - Nov 10, ServerDocs2020: Nov10 - Nov 17, ServerDocs2020: Nov17 - Nov 24

      Description

      I was wondering the impact of readConcern "after/atClusterTimestamp" for user collections in "local" database. Then, realized that
      user writes to (unreplicated) collections in "local" database (except oplog ) are considered as ordered commits and those writes aren’t timestamped. So, reading those collection data with readConcern “after/atClusterTimestamp” doesn’t have any impact. To my surprise, we don't throw any error when a user provides writeConcern (like majority) or readConcern to "local" database collection instead we silently ignore those read-write concern values and execute the operation.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jeffrey.allen Jeffrey Allen
              Reporter:
              suganthi.mani Suganthi Mani
              Participants:
              Last commenter:
              Jeffrey Allen Jeffrey Allen
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                44 weeks, 6 days ago
                Date of 1st Reply: