[
https://issues.apache.org/jira/browse/PHOENIX-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996071#comment-16996071
]
Hadoop QA commented on PHOENIX-5621:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12988839/PHOENIX-5621-4.x-HBase-1.5.patch
against 4.x-HBase-1.5 branch at commit
e7207b96402852440243a0d7d8c7c572cffcd322.
ATTACHMENT ID: 12988839
{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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3191//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3191//console
This message is automatically generated.
> 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
>
> Time Spent: 10m
> 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)
