You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/07/16 20:32:05 UTC

[jira] [Resolved] (HBASE-962) Isolation level support in HBase transactions

     [ 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)