Hadoop QA commented on PHOENIX-5676:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against 4.x-HBase-1.5 branch at commit 
  ATTACHMENT ID: 12991058

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

    {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 
                        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:
    +                    + " (ID INTEGER NOT NULL PRIMARY KEY, NAME VARCHAR, 
+                indexTableTTL = 

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
Console output: 

This message is automatically generated.

> Inline-verification from IndexTool does not handle TTL/row-expiry
> -----------------------------------------------------------------
>                 Key: PHOENIX-5676
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5676
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.15.1, 4.14.3
>            Reporter: Priyank Porwal
>            Assignee: Abhishek Singh Chouhan
>            Priority: Major
>             Fix For: 5.1.0, 4.15.1, 4.16.0
>         Attachments: PHOENIX-5676-4.x-HBase-1.5.002.patch, 
> PHOENIX-5676-4.x-HBase-1.5.patch, PHOENIX-5676-4.x-HBase-1.5.patch, 
> PHOENIX-5676-master.002.patch, PHOENIX-5676-master.patch
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
> If a data-table has TTL on it, it's indexes inherit the TTL too. Hence when 
> we run IndexTool with verification on such tables and it's indexes, rows that 
> are near expiry will successfully get rebuilt, but may not be returned on 
> verification read due to expiry. This will result in index verification 
> problem and may also fail rebuild job.

This message was sent by Atlassian Jira

Reply via email to