You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/17 16:11:00 UTC

[jira] [Resolved] (HBASE-11447) Proposal for a generic transaction API for HBase

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

Andrew Kyle Purtell resolved HBASE-11447.
-----------------------------------------
    Resolution: Won't Fix

> Proposal for a generic transaction API for HBase
> ------------------------------------------------
>
>                 Key: HBASE-11447
>                 URL: https://issues.apache.org/jira/browse/HBASE-11447
>             Project: HBase
>          Issue Type: New Feature
>          Components: Client
>    Affects Versions: 1.0.0
>         Environment: Any.
>            Reporter: John de Roo
>            Priority: Minor
>         Attachments: Proposal for a common transactional API for HBase v0.3_1.pdf, Proposal for a common transactional API for HBase v0.4_1.pdf, Proposal for a common transactional API for HBase v0.5.pdf, Re Proposal for a generic transaction API for HBase.htm
>
>
> HBase transaction management today is provided by a number of products, each implementing a different API, each having different strengths.  The lack of a common API for transactional interfaces means that applications need to be coded to work with a specific Transaction Manager.  This proposal outlines an API which, if implemented by the different Transaction Manager vendors would provide stability and choice to HBase application developers.  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)