Add placementConflictTime to local and remote requests

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • CAR Team 2024-01-22, CAR Team 2024-02-05
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Right now both local and remote requests of a pipeline do not propagate the placementConflictTime to the shards.

      We should propagate it so that transactions fail when they should.

              Assignee:
              Jordi Olivares Provencio
              Reporter:
              Jordi Olivares Provencio
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: