hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "cuijianwei (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11447) Proposal for a generic transaction API for HBase
Date Tue, 22 Jul 2014 02:28:41 GMT

    [ https://issues.apache.org/jira/browse/HBASE-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069715#comment-14069715

cuijianwei commented on HBASE-11447:

v0.5 is cool:)
1. In section 3.2 of v0.5:
only one TransactionService object needs to be instantiated in order to run transactions
Do we need a static TransactionService create/getter method to create a singleton TransactionService
implementation"? Then, different threads could use this singleton implementation more easily.
such as:
   // create or get singleton TransactionService implementation
   public static TransactionService getTransactionService(Configuration config);
2.  In section 4.2:
Isolation levels are based on the ANSI SQL standard.
In the paper "A Critique of ANSI SQL Isolation Levels"(http://research.microsoft.com/apps/pubs/default.aspx?id=69541),
 it proves that: "the ANSI SQL definition fail to characterize several popular isolation levels,....",
the authors provide more accurate descriptions to different isolation levels including Snapshot
Isolation for multi-version system(the isolation levels are concluded in Table 4 in the paper),
do we need to cite this paper to define the isolation levels?

> 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: features, newbie
>             Fix For: 1.0.0
>         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

View raw message