[
https://issues.apache.org/jira/browse/HBASE-18144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033273#comment-16033273
]
Esteban Gutierrez commented on HBASE-18144:
-------------------------------------------
Yeah, per table sounds a reasonable approach. I've been thinking that the
locking mechanism could be pluggable so we can keep multiple implementations
and each could be better suited for some workloads. I don't think is overkill
to do that but that would be an option.
> 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)
