[
https://issues.apache.org/jira/browse/PHOENIX-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015354#comment-17015354
]
Hadoop QA commented on PHOENIX-5651:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12990908/PHOENIX-5651.master.v1.patch
against master branch at commit 6405839b60c410292c0e2c8cbbdee55d09343bab.
ATTACHMENT ID: 12990908
{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:red}-1 javac{color}. The patch appears to cause mvn compile goal to
fail .
Compilation errors resume:
[ERROR] COMPILATION ERROR :
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-PHOENIX-Build/phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexScrutinyToolIT.java:[426,33]
cannot find symbol
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
(default-testCompile) on project phoenix-core: Compilation failure
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-PHOENIX-Build/phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexScrutinyToolIT.java:[426,33]
cannot find symbol
[ERROR] symbol: variable Sets
[ERROR] location: class org.apache.phoenix.end2end.IndexScrutinyToolIT
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :phoenix-core
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3291//console
This message is automatically generated.
> IndexScrutiny does not handle TTL/row-expiry
> --------------------------------------------
>
> Key: PHOENIX-5651
> URL: https://issues.apache.org/jira/browse/PHOENIX-5651
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.15.1, 4.14.3
> Reporter: Priyank Porwal
> Assignee: Swaroopa Kadam
> Priority: Major
> Fix For: 4.15.1, 4.16.0
>
> Attachments: PHOENIX-5651.4.x-HBase-1.3.patch,
> PHOENIX-5651.4.x-HBase-1.3.v1.patch, PHOENIX-5651.4.x-HBase-1.3.v2.patch,
> PHOENIX-5651.master.v1.patch
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> If a data-table has TTL on it, it's indexes inherit the TTL too. Hence when
> we run IndexScrutiny on such tables and it's indexes, scrutiny's attempts to
> find matching index rows for near-expiry data rows results in no-matches
> since the index row gets expired before the read from data-region mapper. The
> same happens in the MR job for the other direction Index->Data.
> This does not impact correctness of indexing design, but makes it very
> inconvenient to get a clean scrutiny run. All reported invalid rows have to
> be matched against the table TTL, which is non-trivial exercise.
> IndexScrutiny itself could detect such expired rows when the matching pair is
> not found and not report them as INVALID_ROWS. Perhaps a new counter for
> EXPIRED_ROWS should be added as well for better visibility.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
