[
https://issues.apache.org/jira/browse/PHOENIX-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532734#comment-15532734
]
Ankit Singhal commented on PHOENIX-3254:
----------------------------------------
{code}
-1 core tests. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.tx.TransactionIT
{code}
Not sure, It is related to this.
Running QA bot again with v1.
> 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
> Fix For: 4.9.0
>
> Attachments: PHOENIX-3254.patch, PHOENIX-3254_v1.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)
