[
https://issues.apache.org/jira/browse/PHOENIX-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148276#comment-17148276
]
Hadoop QA commented on PHOENIX-5210:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/13006698/PHOENIX-5210.master.v3.patch
against master branch at commit 0bbe2faddce0b9b550a8efd558536bb03cfb133f.
ATTACHMENT ID: 13006698
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified tests.
{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.IndexToolForNonTxGlobalIndexIT
{color:red}-1 core zombie tests{color}. There are 7 zombie test(s):
at
org.apache.phoenix.end2end.UpsertSelectIT.testUpsertSelectWithSequence(UpsertSelectIT.java:832)
at
org.apache.phoenix.end2end.RowValueConstructorOffsetIT.testRVCOffsetMoreThanKey(RowValueConstructorOffsetIT.java:272)
at
org.apache.phoenix.end2end.index.BaseIndexIT.testInFilterOnIndexedTable(BaseIndexIT.java:1040)
at
org.apache.phoenix.end2end.index.MutableIndexSplitIT.testSplitDuringIndexScan(MutableIndexSplitIT.java:83)
at
org.apache.phoenix.end2end.index.MutableIndexSplitForwardScanIT.testSplitDuringIndexScan(MutableIndexSplitForwardScanIT.java:30)
at
org.apache.phoenix.end2end.index.BaseIndexIT.testSelectDistinctOnTableWithSecondaryImmutableIndex(BaseIndexIT.java:443)
at
org.apache.phoenix.end2end.index.BaseIndexIT.testSelectAllAndAliasWithIndex(BaseIndexIT.java:596)
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/4006//testReport/
Code Coverage results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/4006//artifact/phoenix-core/target/site/jacoco/index.html
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/4006//console
This message is automatically generated.
> NullPointerException when alter options of a table that is appendOnlySchema
> ---------------------------------------------------------------------------
>
> Key: PHOENIX-5210
> URL: https://issues.apache.org/jira/browse/PHOENIX-5210
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.15.0, 4.14.3
> Reporter: Toshihiro Suzuki
> Assignee: Toshihiro Suzuki
> Priority: Major
> Fix For: 4.16.0
>
> Attachments: PHOENIX-5210.master.v3.patch
>
>
> I'm facing the following NullPointerException when alter options of a table
> that is appendOnlySchema.
> {code}
> java.lang.NullPointerException
> at
> org.apache.phoenix.schema.MetaDataClient.addColumn(MetaDataClient.java:3545)
> at
> org.apache.phoenix.schema.MetaDataClient.addColumn(MetaDataClient.java:3517)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$ExecutableAddColumnStatement$1.execute(PhoenixStatement.java:1440)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:408)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:391)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:390)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:378)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1833)
> at
> org.apache.phoenix.end2end.AppendOnlySchemaIT.testAlterTableOptions(AppendOnlySchemaIT.java:368)
> {code}
> Steps to reproduce is as follows:
> 1. Create a table that is appendOnlySchema:
> {code}
> CREATE TABLE tbl (id INTEGER PRIMARY KEY, col INTEGER) APPEND_ONLY_SCHEMA =
> true, UPDATE_CACHE_FREQUENCY = 1;
> {code}
> 2. Alter a option of the table:
> {code}
> ALTER TABLE tbl SET STORE_NULLS = true;
> {code}
> After step 2, we will face the NullPointerException.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
