[
https://issues.apache.org/jira/browse/PHOENIX-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3791:
----------------------------------
Description:
A corner case related to PHOENIX-3789. Transactional, mutable secondary index
maintenance writes to the index table in the preBatchMutation while the row
locks are still held which should be avoided.
This can be fixed by either leveraging a way of passing state between
coprocessor hooks (which I'm not sure exists) or through thread locals as a
last resort.
was:
A corner case related to PHOENIX-3789. Non transactional, mutable secondary
index maintenance relies on the the WAL edit as state so that the actual index
writes can be done later. When WAL edits are disabled, the writes to the index
table are done in the preBatchMutation while the row locks are still held which
should be avoided.
This can be fixed by either leveraging a way of passing state between
coprocessor hooks (which I'm not sure exists) or through thread locals as a
last resort.
> Execute cross region index maintenance calls outside of row lock for
> transactional tables
> -----------------------------------------------------------------------------------------
>
> Key: PHOENIX-3791
> URL: https://issues.apache.org/jira/browse/PHOENIX-3791
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
>
> A corner case related to PHOENIX-3789. Transactional, mutable secondary index
> maintenance writes to the index table in the preBatchMutation while the row
> locks are still held which should be avoided.
> This can be fixed by either leveraging a way of passing state between
> coprocessor hooks (which I'm not sure exists) or through thread locals as a
> last resort.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
