[
https://issues.apache.org/jira/browse/PHOENIX-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-4053:
----------------------------------
Description: From HBase 1.2 on, rows are not exclusively locked when the
preBatchMutate call is made (see HBASE-18474). The mutable secondary index
(global and local) depend on this to get a consistent snapshot of a row between
the point when the current row value is looked up, and when the new row is
written. (was: In HBase 1.3, it turns out that rows are not exclusively locked
when the preBatchMutate call is made. The mutable secondary index (global and
local) depend on this to get a consistent snapshot of a row. This will likely
get fixed in HBASE-18474, but we need to guard against this ourselves.)
> Lock row exclusively when necessary for mutable secondary indexing
> ------------------------------------------------------------------
>
> Key: PHOENIX-4053
> URL: https://issues.apache.org/jira/browse/PHOENIX-4053
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Attachments: PHOENIX-4053_wip.patch
>
>
> From HBase 1.2 on, rows are not exclusively locked when the preBatchMutate
> call is made (see HBASE-18474). The mutable secondary index (global and
> local) depend on this to get a consistent snapshot of a row between the point
> when the current row value is looked up, and when the new row is written.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
