[
https://issues.apache.org/jira/browse/PHOENIX-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16146910#comment-16146910
]
Andrew Purtell commented on PHOENIX-4138:
-----------------------------------------
That's my point exactly - the client can supply their own value. By definition
this is not a hard limit. A hard limit is one that cannot be changed by the
user. A server side mechanism is required to assure the check is always made
and the set value cannot be changed by a client configuration update or code
patch.
> 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: Rahul Shrivastava
> 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)
