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

Hadoop QA commented on PHOENIX-4988:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12945078/PHOENIX-4988.v1.4.x-HBase-1.4.patch
  against 4.x-HBase-1.4 branch at commit 
e07e04a54a6720a0ba8e7a806cd98a2ebc8b2d17.
  ATTACHMENT ID: 12945078

    {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:red}-1 lineLengths{color}.  The patch introduces the following lines 
longer than 100:
    +          conn.createStatement().execute("CREATE TABLE " + fullTableName + 
" (k VARCHAR NOT NULL PRIMARY KEY, v1 VARCHAR, v2 VARCHAR) " + tableDDLOptions);
+          conn.createStatement().execute("CREATE " + (localIndex ? " LOCAL " : 
"") + " INDEX " + indexName + " ON " + fullTableName + " (v2)");
+          conn.createStatement().executeUpdate("UPSERT INTO " + fullTableName 
+ "(k,v1,v2) VALUES ('testKey','v1_1','v2_1')");
+          conn.createStatement().executeUpdate("UPSERT INTO " + fullTableName 
+ "(k,v1,v2) VALUES ('testKey','v1_2','v2_2')");
+          conn.createStatement().executeUpdate("UPSERT INTO " + fullTableName 
+ "(k,v1) VALUES ('testKey','v1_3')");
+          conn.createStatement().executeUpdate("UPSERT INTO " + fullTableName 
+ "(k,v1,v2) VALUES ('testKey','v1_4','v2_3')");
+      if (coveringDelete.deleteFamily == null || 
!CellUtil.matchingFamily(coveringDelete.deleteFamily, nextKV)) {

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

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

This message is automatically generated.

> Incorrect index rowkey generated when updating only non-indexed columns after 
> a delete
> --------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4988
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4988
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.0
>            Reporter: Vincent Poon
>            Assignee: Vincent Poon
>            Priority: Critical
>             Fix For: 4.14.1
>
>         Attachments: PHOENIX-4988.v1.4.x-HBase-1.4.patch, 
> PHOENIX-4988.v1.master.patch
>
>
> The following steps result in an incorrect index rowkey being generated after 
> an index update to a non-indexed column. 
> create table test (k VARCHAR NOT NULL PRIMARY KEY, v1 VARCHAR, v2 VARCHAR)
> create index test_ind ON test (v2)
> upsert into test (k,v1,v2) VALUES ('testKey','v1_1','v2_1');
> delete from test;
> upsert into test (k,v1,v2) VALUES ('testKey','v1_2','v2_2');
> delete from test;
> upsert into test (k,v1) VALUES ('testKey','v1_3');



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to