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

Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2017/06/01 14:16:04 UTC

[jira] [Comment Edited] (HBASE-18144) Forward-port the old exclusive row lock; there are scenarios where it performs better

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

Sean Busbey edited comment on HBASE-18144 at 6/1/17 2:15 PM:
-------------------------------------------------------------

so the locking would be chosen per-table, rather than deployment wide? what about at a namespace level?


was (Author: busbey):
so the locking would be chosen per-table, rather than implementation wide? what about at a namespace level?

> Forward-port the old exclusive row lock; there are scenarios where it performs better
> -------------------------------------------------------------------------------------
>
>                 Key: HBASE-18144
>                 URL: https://issues.apache.org/jira/browse/HBASE-18144
>             Project: HBase
>          Issue Type: Bug
>          Components: Increment
>    Affects Versions: 1.2.5
>            Reporter: stack
>            Assignee: stack
>             Fix For: 2.0.0, 1.3.2, 1.2.7
>
>
> Description to follow.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)