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

remove afterOpTime readConcern argument

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Catalog and Routing
    • 2

      Currently there could be afterClusterTime and afterOpTime arguments.
      Those arguments can be merged.
      While afterOpTime uses an opTime , the "term" argument is not used as the afterOpTime reads are always with level = majority.

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            misha.tyulenev@mongodb.com Misha Tyulenev
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: