You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "jaanai (JIRA)" <ji...@apache.org> on 2019/05/19 02:46:00 UTC

[jira] [Updated] (PHOENIX-5207) Create index if not exists fails incorrectly if table has 'maxIndexesPerTable' indexes already

     [ https://issues.apache.org/jira/browse/PHOENIX-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaanai updated PHOENIX-5207:
----------------------------
    Fix Version/s: 5.0.1

> 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.15.0, 5.1.0, 4.14.2, 5.0.1
>
>         Attachments: PHOENIX-5207-4.14-HBase-1.4.patch, PHOENIX-5207-master.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)