[
https://issues.apache.org/jira/browse/HBASE-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207987#comment-14207987
]
cuijianwei commented on HBASE-11447:
------------------------------------
I tried to make Themis(https://github.com/XiaoMi/themis/) implement v5.0, the
core abstraction is feasible for Themis implementation generally. There are
some changes Themis needs to do, including add a TransactonService implement
class to handle global HConnection and ThreadPool, etc. I thinks there are some
issues need to be discussed as [~ghelmling] mentioned, including is it possible
to add a close() method into TransactonService to release global resource at
the end? Will we continue to improve the proposal?
> 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
> Labels: beginner
> 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
(v6.3.4#6332)
