You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Kadir OZDEMIR (Jira)" <ji...@apache.org> on 2019/11/08 10:06:00 UTC
[jira] [Created] (PHOENIX-5563) Multiple mutations on a row within
a batch should be treated as concurrent
Kadir OZDEMIR created PHOENIX-5563:
--------------------------------------
Summary: Multiple mutations on a row within a batch should be treated as concurrent
Key: PHOENIX-5563
URL: https://issues.apache.org/jira/browse/PHOENIX-5563
Project: Phoenix
Issue Type: Bug
Affects Versions: 5.1.0
Reporter: Kadir OZDEMIR
Assignee: Kadir OZDEMIR
In the current implementation of IndexRegionObserver, only mutations from different batches are considered concurrent if they are updating the same row. However, if there are multiple mutations on the same row within the same batch, these mutations should also be considered concurrent since these mutations are processed individually and their updates on the data table are not visible to each other.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)