[
https://issues.apache.org/jira/browse/PHOENIX-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000479#comment-17000479
]
Hudson commented on PHOENIX-5640:
---------------------------------
SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #626 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/626/])
PHOENIX-5640 Pending disable count should not be increased for rebuild (kadir:
rev ba7bee3f86e3d67cc07383e6f8d52e4c9e889f90)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/index/PhoenixIndexFailurePolicy.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/index/MutableIndexRebuilderIT.java
* (edit) phoenix-core/src/test/java/org/apache/phoenix/util/TestUtil.java
> 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
> Fix For: 4.15.1
>
> 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)
