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

Transaction does not need to be encoded for every operation

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 0.12.0-incubating
    • 0.13.0-incubating
    • None
    • None

    Description

      If a transaction performs multiple operations, the transaction object is encoded for the call to HBase every time. If there are many invalid transactions, this can be unnecessary overhead. Instead, the TransactionAwareHTable could cache the encoded transaction and reuse it for subsequent calls.

      Attachments

        Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. TEPHRA-247 Avoid encoding the transaction multiple times

          • Major - Major loss of function.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. TEPHRA-232 Transaction metadata sent on each put is too big

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            People

              poorna Poorna Chandra
              anew Andreas Neumann
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: