phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (PHOENIX-4053) Lock row exclusively when necessary for mutable secondary indexing
Date Fri, 28 Jul 2017 20:42:00 GMT

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

James Taylor reassigned PHOENIX-4053:
-------------------------------------

    Assignee: James Taylor

> 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
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message