[
https://issues.apache.org/jira/browse/PHOENIX-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374806#comment-15374806
]
Hadoop QA commented on PHOENIX-3061:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12817629/PHOENIX-3061_addendum3.patch
against master branch at commit 8346c470fff04b2b6bab57ecfba93c9879afad7e.
ATTACHMENT ID: 12817629
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
35 warning messages.
{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("upsert into " + tableName + "
(pk1, pk2, pk3) values ('a', '1', '1')");
+ conn.createStatement().execute("upsert into " + tableName + "
(pk1, pk2, pk3) values ('b', '2', '2')");
+ conn.createStatement().execute("CREATE INDEX " + indexName + " ON
" + tableName + " (pk3, pk2) ASYNC");
+ <argLine>-enableassertions -Xmx2000m -XX:MaxPermSize=128m
-Djava.security.egd=file:/dev/./urandom
"-Djava.library.path=${hadoop.library.path}${path.separator}${java.library.path}"</argLine>
{color:red}-1 core tests{color}. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.AsyncImmutableIndexIT
{color:red}-1 core zombie tests{color}. There are 5 zombie test(s):
at
org.apache.hadoop.hbase.client.TestSizeFailures.testScannerSeesAllRecords(TestSizeFailures.java:123)
at
org.apache.hadoop.hbase.client.TestSplitOrMergeStatus.testMergeSwitch(TestSplitOrMergeStatus.java:128)
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/442//testReport/
Javadoc warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/442//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/442//console
This message is automatically generated.
> IndexTool marks index as ACTIVE and exit 0 even if bulkload has error
> ---------------------------------------------------------------------
>
> Key: PHOENIX-3061
> URL: https://issues.apache.org/jira/browse/PHOENIX-3061
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.7.0
> Reporter: Tongzhou Wang
> Assignee: Tongzhou Wang
> Priority: Blocker
> Labels: easyfix
> Fix For: 4.8.0
>
> Attachments: PHOENIX-3061_addendum2.patch,
> PHOENIX-3061_addendum3.patch, PHOENIX-3061_addendum4.patch, fix.diff
>
>
> In `IndexTool`, the job exits with code 0 and marks the index table as ACTIVE
> even though MapReduce had error.
> See:
> https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexTool.java#L246-L256
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
