[change streams] Adjust resume token (if necessary) for sharded transactions

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Aggregation Framework
    • None
    • Query
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Depending on the format of a transaction in the oplog, we will likely have to update the format of the resume token to ensure we have a total ordering across all operations, particularly those that commit as part of a distributed, multi-document transaction.

              Assignee:
              Backlog - Query Team (Inactive)
              Reporter:
              Charlie Swanson
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: