[
https://issues.apache.org/jira/browse/PHOENIX-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-4138:
----------------------------------
Attachment: PHOENIX-4138_v3.patch
Tweaked your patch, [~churromorales]. You can't override the
MAX_INDEXES_PER_TABLE property because it'll impact other tests (the mini
cluster is shared between many test classes). Also, you forgot to add a fail()
call after the second index creation (so it'd always succeed).
> Create a hard limit on number of indexes per table
> --------------------------------------------------
>
> Key: PHOENIX-4138
> URL: https://issues.apache.org/jira/browse/PHOENIX-4138
> Project: Phoenix
> Issue Type: Bug
> Reporter: Rahul Shrivastava
> Assignee: churro morales
> Attachments: PHOENIX-4138.patch, PHOENIX-4138.v1.patch,
> PHOENIX-4138.v2.patch, PHOENIX-4138_v3.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> There should be a config parameter to impose a hard limit on number of
> indexes per table. There is a SQL Exception
> https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/exception/SQLExceptionCode.java#L260
> , but it gets triggered on the server side
> (https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java#L1589)
> .
> We need a client side limit that can be configured via Phoenix config
> parameter. Something like if user create more than lets say 30 indexes per
> table, it would not allow more index creation for the that specific table.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
