[ https://issues.apache.org/jira/browse/PHOENIX-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15525597#comment-15525597 ]
ASF GitHub Bot commented on PHOENIX-3254: ----------------------------------------- GitHub user ankitsinghal opened a pull request: https://github.com/apache/phoenix/pull/211 PHOENIX-3254 IndexId Sequence is incremented even if index exists alr… …eady You can merge this pull request into a Git repository by running: $ git pull https://github.com/ankitsinghal/phoenix PHOENIX-3254 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/phoenix/pull/211.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #211 ---- commit 5268a90d38c21e8f93b8b2782f2d9e146642a463 Author: Ankit Singhal <ankitsingha...@gmail.com> Date: 2016-09-27T09:29:11Z PHOENIX-3254 IndexId Sequence is incremented even if index exists already ---- > IndexId Sequence is incremented even if index exists already. > ------------------------------------------------------------- > > Key: PHOENIX-3254 > URL: https://issues.apache.org/jira/browse/PHOENIX-3254 > Project: Phoenix > Issue Type: Bug > Reporter: Ankit Singhal > Assignee: Ankit Singhal > Attachments: PHOENIX-3254.patch, PHOENIX-3254_wip.patch > > > As we are incrementing sequence at the client even if we are not going to > create a index (in case index already exists and user is using CREATE INDEX > IF NOT EXISTS) or DDL failed in later stage(due to parent table not found or > something). > If this keeps on happening then user may reach the limit of Short.MAX_VALUE > and TOO_MANY_INDEXES exception will be thrown if user tries to create a new > index. > To prevent, this we should increment sequences when we are about to create a > index at server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)