[
https://issues.apache.org/jira/browse/PHOENIX-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997587#comment-16997587
]
Hudson commented on PHOENIX-5621:
---------------------------------
SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-1.5 #220 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.5/220/])
PHOENIX-5621 - IndexUpgradeTool uses wrong priority and unnecessary (gjacoby:
rev a2adf5e572c5a4bcccee7f8ac43bad6b84293ec6)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexUpgradeTool.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/ParameterizedIndexUpgradeToolIT.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/index/IndexCoprocIT.java
> IndexUpgradeTool uses wrong priority for GlobalIndexChecker
> -----------------------------------------------------------
>
> Key: PHOENIX-5621
> URL: https://issues.apache.org/jira/browse/PHOENIX-5621
> Project: Phoenix
> Issue Type: Bug
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Blocker
> Fix For: 4.15.0, 5.1.0, 4.14.4
>
> Attachments: PHOENIX-5621-4.x-HBase-1.5.patch, PHOENIX-5621.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The GlobalIndexChecker is meant to run first amongst all coprocs on an index
> table, but the index upgrade tool assigns it to the default priority.
> Depending on load order, this can result in other coprocs running first which
> can result in incorrect behavior.
> Fix is trivial, just subtract 1 as is done in CQSI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
