[
https://issues.apache.org/jira/browse/HBASE-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358727#comment-14358727
]
Ashish Singhi commented on HBASE-13220:
---------------------------------------
bq. what if the quota is about maximum number of region that can be created or
replicas or some other on-creation configuration? an admin may want to enforce
that creation of Table-X will not exceed that number.
what ever it is, shouldn't this be set on a existing table or a namespace ?
bq. what about people who is using the java API?
I will handle this in next patch. Need to add the existence check in most of
the API's in QuotaSettingsFactory class.
> set_quota should fail for non-existing table and namespace
> ----------------------------------------------------------
>
> Key: HBASE-13220
> URL: https://issues.apache.org/jira/browse/HBASE-13220
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Ashish Singhi
> Assignee: Ashish Singhi
> Labels: quota
> Fix For: 2.0.0
>
> Attachments: HBASE-13220.patch
>
>
> set_quota command to should throw exception to user when trying to set quota
> on a non-existing table or namespace same like grant command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
