[jira] [Commented] (PHOENIX-5563) Multiple mutations on a row within a batch should be treated as concurrent

["Hadoop QA (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970135#comment-16970135 ] 

Hadoop QA commented on PHOENIX-5563:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12985336/PHOENIX-5563.master.001.patch
  against master branch at commit 70baf4c6805eb46420dd1fbaf71a093ab7d84a8b.
  ATTACHMENT ID: 12985336

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexIT

Test results: https://builds.apache.org/job/PreCommit-PHOENIX-Build/3102//testReport/
Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/3102//console

This message is automatically generated.

> 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
>            Priority: Major
>         Attachments: PHOENIX-5563.master.001.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)