Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 16 Jul 2014 18:32:05 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12407293.1225129201665.55952.1405535525977@arcas>
In-Reply-To: <JIRA.12407293.1225129201665@arcas>
References: <JIRA.12407293.1225129201665@arcas>
Subject: [jira] [Resolved] (HBASE-962) Isolation level support in HBase
 transactions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack resolved HBASE-962.
-------------------------

    Resolution: Later

Resolving as 'later'.  Issue is stale.  Won't do different isolation levels in hbase, at least not in foreseeable future, but may do so on top of hbase.

> Isolation level support in HBase transactions
> ---------------------------------------------
>
>                 Key: HBASE-962
>                 URL: https://issues.apache.org/jira/browse/HBASE-962
>             Project: HBase
>          Issue Type: Improvement
>          Components: io, IPC/RPC, regionserver
>            Reporter: Jaeyun Noh
>
> There will be some case that we don't strict transaction isolation level. Just a ReadCommitted iso-level will be sufficient in some application. (Non-repeatable read, phantom possible)
> And, it would be great to specify which isolation level will be used in HBase transaction by an enumeration.


--
This message was sent by Atlassian JIRA
(v6.2#6252)