Uploaded image for project: 'Phoenix Tephra'
  1. Phoenix Tephra
  2. TEPHRA-98

Separate transaction ID from write pointer

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.5.0
    • api, core
    • None

    Description

      Currently we use a transaction's write pointer as the way it is identified everywhere to the transaction service. This works in the case of a single stage transaction (where a single write pointer is used), but will not work if we want to support checkpointed transactions which may have multiple write pointers. For checkpointed transactions we will want to clearly distinguish between the current write pointer being used (which will change after a checkpoint) vs. how the transaction is identified to the system (which will remain the same).

      Attachments

        Activity

          People

            ghelmling Gary Helmling
            ghelmling Gary Helmling
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: