Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-35821

readConcern:snapshot transactions need a read timestamp <= WT's all_committed point

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v4.0
    • Repl 2018-07-16, Repl 2018-08-27, Repl 2018-09-10, Repl 2018-09-24

    Attachments

      Issue Links

        depends on

        New Feature - A new feature of the product, which has yet to be developed. WT-4176 Expose a WT_SESSION.query_timestamp method

        • Major - P3 - Major loss of function.
        • Closed
        is documented by

        Improvement - An improvement or enhancement to an existing feature or task. DOCS-12555 txn read concern: read concern local and majority

        • Major - P3 - Major loss of function.
        • Closed
        related to

        Bug - A problem which impairs or prevents the functions of the product. SERVER-35798 Writing an oplog entry for prepare should not push the lastApplied timestamp

        • Major - P3 - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. SERVER-40123 Transaction diagnostics should not report upconverted readConcern

        • Major - P3 - Major loss of function.
        • Closed

        Task - A task that needs to be done. SERVER-39260 Uncomment test at the bottom of jstests/core/txns/timestamped_reads_wait_for_prepare_oplog_visibility.js

        • Major - P3 - Major loss of function.
        • Closed

        Task - A task that needs to be done. SERVER-42547 Complete TODO listed in SERVER-35821

        • Major - P3 - Major loss of function.
        • Closed

        Activity

          People

            matthew.russotto@mongodb.com Matthew Russotto
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: