[
https://issues.apache.org/jira/browse/PHOENIX-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999865#comment-16999865
]
Hadoop QA commented on PHOENIX-5640:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12989165/PHOENIX-5640.4.x-HBase-1.5.001.patch
against 4.x-HBase-1.5 branch at commit
ac6831fe32ecfc44ee0cf160d361f04b6afd5894.
ATTACHMENT ID: 12989165
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3202//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3202//console
This message is automatically generated.
> Pending disable count should not be increased for rebuild write failures
> ------------------------------------------------------------------------
>
> Key: PHOENIX-5640
> URL: https://issues.apache.org/jira/browse/PHOENIX-5640
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.14.3
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
> Attachments: PHOENIX-5640.4.x-HBase-1.5.001.patch
>
>
> For index rebuild write failures, PhoenixIndexFailurePolicy does not change
> the index state but unnecessarily increases the pending disable count that is
> maintained in the system catalog. This leads to system catalog corruption
> when view indexes experience index rebuild write failures. This is because
> PhoenixIndexFailurePolicy uses the physical table name instead of the logical
> table name when updating the system catalog.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
