Use OperationId instead of LogicalSessionId in the BucketCatalog

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc5, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • ALL
    • v5.0
    • Execution Team 2021-06-28
    • 150
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently in the bucket catalog, we use LogicalSessionId to keep inserts separated per operation. However, it is not guaranteed that a LogicalSessionId will always be supplied. We should instead use OperationId for this.

            Assignee:
            Gregory Noma
            Reporter:
            Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: