Store logical session id and transaction number on the OperationContext

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.5.10
    • Affects Version/s: 3.5.9
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-07-10
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The lsid and txnNumber fields will become legitimate top-level values for all commands. As such, there should be code just after command parsing, but before authentication (so the sessionId is available to the auth system), which extracts these fields and sets them on the OperationContext.

              Assignee:
              Kaloian Manassiev
              Reporter:
              Kaloian Manassiev
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: