[
https://issues.apache.org/jira/browse/PHOENIX-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801397#comment-16801397
]
Hadoop QA commented on PHOENIX-5207:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12963679/PHOENIX-5207-4.14-HBase-1.4.patch
against 4.14-HBase-1.4 branch at commit
69e5bb0b304a53967cef40b2a4cfc66e69ecaa51.
ATTACHMENT ID: 12963679
{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:red}-1 core tests{color}. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.join.HashJoinMoreIT
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2456//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2456//console
This message is automatically generated.
> Create index if not exists fails incorrectly if table has
> 'maxIndexesPerTable' indexes already
> -----------------------------------------------------------------------------------------------
>
> Key: PHOENIX-5207
> URL: https://issues.apache.org/jira/browse/PHOENIX-5207
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.1
> Reporter: Abhishek Singh Chouhan
> Assignee: Abhishek Singh Chouhan
> Priority: Major
> Fix For: 4.14.2
>
> Attachments: PHOENIX-5207-4.14-HBase-1.4.patch
>
>
> If a table has 'maxIndexesPerTable' indexes and we try to create another one
> and if it already exists we should not throw 'ERROR 1047 (43A04): Too many
> indexes have already been created' since weve put 'if not exists' already in
> the statement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
