Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 86B3A11BD4 for ; Tue, 1 Jul 2014 03:10:25 +0000 (UTC) Received: (qmail 34747 invoked by uid 500); 1 Jul 2014 03:10:24 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 34700 invoked by uid 500); 1 Jul 2014 03:10:24 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 34689 invoked by uid 99); 1 Jul 2014 03:10:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jul 2014 03:10:24 +0000 Date: Tue, 1 Jul 2014 03:10:24 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11447) Proposal for a generic transaction API for HBase MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048456#comment-14048456 ] Ted Yu commented on HBASE-11447: -------------------------------- @John: Can you attach the pdf to this JIRA ? Thanks > 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 > > > 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. > A current copy of the: [file:///C:/JdRsFiles/Trafodine/Open Source/Open Transaction Interface.pdf] > > -- This message was sent by Atlassian JIRA (v6.2#6252)