[
https://issues.apache.org/jira/browse/HBASE-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358788#comment-14358788
]
Matteo Bertozzi commented on HBASE-13220:
-----------------------------------------
{quote}This looks like it was done intentionally. Can I know the reason ? So
that if it was done purposefully I can invalid this jira.{quote}
there reason was the above, you may want to enforce quotas and rules on
something that will be created in the future.
e.g. allow only 1 replica for table named "test-xyz", allow maximum 4 regions
for... and so on.
those information doesn't make sense at an upper level level (e.g. namespace),
but are just specific to the object (e.g. table)
> 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
> Priority: Minor
> 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)
