Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@locus.apache.org Received: (qmail 95281 invoked from network); 6 Jun 2008 00:09:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Jun 2008 00:09:07 -0000 Received: (qmail 51880 invoked by uid 500); 6 Jun 2008 00:09:09 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 51864 invoked by uid 500); 6 Jun 2008 00:09:09 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 51853 invoked by uid 99); 6 Jun 2008 00:09:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2008 17:09:09 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jun 2008 00:08:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 952E4234C12F for ; Thu, 5 Jun 2008 17:08:45 -0700 (PDT) Message-ID: <69324734.1212710925609.JavaMail.jira@brutus> Date: Thu, 5 Jun 2008 17:08:45 -0700 (PDT) From: "Clint Morgan (JIRA)" To: hbase-dev@hadoop.apache.org Subject: [jira] Created: (HBASE-669) MultiRegion transactions with Optimistic Concurrency Control MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org MultiRegion transactions with Optimistic Concurrency Control ------------------------------------------------------------ Key: HBASE-669 URL: https://issues.apache.org/jira/browse/HBASE-669 Project: Hadoop HBase Issue Type: New Feature Components: client, ipc, regionserver Reporter: Clint Morgan We have a need for ACID transactions across tables. This issue is about adding transactions which span multiple regions. We do not envision many competing writes, and will be read-dominated in general. This makes Optimistic Concurrency Control (OCC) seem like the way to go. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.