[
https://issues.apache.org/jira/browse/PHOENIX-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011290#comment-17011290
]
Hadoop QA commented on PHOENIX-5666:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12990257/PHOENIX-5666.master.001.patch
against master branch at commit ae85b069058b19e6c1729a4767d762e8f2c48b5d.
ATTACHMENT ID: 12990257
{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: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:
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3254//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3254//console
This message is automatically generated.
> IndexRegionObserver incorrectly updates PostIndexUpdateFailure metric
> ---------------------------------------------------------------------
>
> Key: PHOENIX-5666
> URL: https://issues.apache.org/jira/browse/PHOENIX-5666
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.14.3
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
> Attachments: PHOENIX-5666.master.001.patch
>
>
> When there is no post index (phase 3) updates (for tables with no indexes or
> during index rebuild), the list for index updates is not initialized by
> IndexRegionObserver. This causes a null pointer exception and this exception
> is caught and ignored since phase3 write failures are in general ignored.
> However, this leads to updating the PostIndexUpdateFailure metric incorrectly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
