Add invariant that a transaction's read timestamp satisfies read concern constraints

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Replication
    • v4.4, v4.2
    • 35
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a startTransaction comes in with an afterClusterTime, we never validate that the readTimestamp captured here actually satisfied the afterClusterTime.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: