[
https://issues.apache.org/jira/browse/PHOENIX-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697917#comment-16697917
]
Hadoop QA commented on PHOENIX-4971:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12949394/PHOENIX-4971-4.x-HBase-1.1-v6.patch
against master branch at commit 6214c79f08ae5a106262fc8a1c644d3a4b34c7e2.
ATTACHMENT ID: 12949394
{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:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2166//console
This message is automatically generated.
> Drop index will execute successfully using Incorrect name of parent tables
> --------------------------------------------------------------------------
>
> Key: PHOENIX-4971
> URL: https://issues.apache.org/jira/browse/PHOENIX-4971
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.1
> Reporter: Jaanai
> Assignee: Jaanai
> Priority: Major
> Fix For: 4.15.0
>
> Attachments: PHOENIX-4971-4.x-HBase-1.1-v6.patch,
> PHOENIX-4971-4.x-HBase-1.2-v6.patch, PHOENIX-4971-4.x-HBase-1.3-v6.patch,
> PHOENIX-4971-4.x-HBase-1.4-v6.patch, PHOENIX-4971-master-v2.patch,
> PHOENIX-4971-master-v3.patch, PHOENIX-4971-master-v4.patch,
> PHOENIX-4971-master-v5-it-fixed.patch, PHOENIX-4971-master-v6.patch,
> PHOENIX-4971-master.patch
>
>
> The blew SQL will be executed successfully, the name of data tables is
> incorrectly inputted that the parent table has the same name with index
> tables.
>
> {code:java}
> DROP INDEX INDEX_TABLE_X on INDEX_TABLE_X;
> {code}
> Some regions will not online and some queries will not normally execute after
> executing above SQL. Everything will be ok unless manually delete dirty
> metadata information in SYSTEM.CATALOG table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
