phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3254) IndexId Sequence is incremented even if index exists already.
Date Wed, 02 Nov 2016 20:07:58 GMT


Hudson commented on PHOENIX-3254:

FAILURE: Integrated in Jenkins build Phoenix-master #1468 (See [])
PHOENIX-3433 Local or view indexes cannot be created after PHOENIX-3254 (rajeshbabu: rev 8a44cc00101e44e0afd2cadb2b5a4a1eba6052fe)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/coprocessor/
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/

> IndexId Sequence is incremented even if index exists already.
> -------------------------------------------------------------
>                 Key: PHOENIX-3254
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message