tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Neumann (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TEPHRA-233) Transaction does not need to be encoded for every operation
Date Fri, 08 Sep 2017 20:49:00 GMT

     [ https://issues.apache.org/jira/browse/TEPHRA-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Neumann resolved TEPHRA-233.
------------------------------------
       Resolution: Duplicate
    Fix Version/s: 0.13.0-incubating

> Transaction does not need to be encoded for every operation
> -----------------------------------------------------------
>
>                 Key: TEPHRA-233
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-233
>             Project: Tephra
>          Issue Type: Improvement
>    Affects Versions: 0.12.0-incubating
>            Reporter: Andreas Neumann
>            Assignee: Poorna Chandra
>             Fix For: 0.13.0-incubating
>
>
> 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. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message