[
https://issues.apache.org/jira/browse/HBASE-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605587#comment-14605587
]
Matteo Bertozzi commented on HBASE-13987:
-----------------------------------------
that isQuotaEnabled() checking the configuration is not what you want.
on the client conf you set hbase.quota.enabled = true, but on the server side
you have hbase.quota.enabled = false you still end up with TableNotFound.
set_quota ask the server if the conf is enabled or not, in this patch you ask
the client which is not correct.
if you want to add a check just check for TableNotFound.
> Modify the result of shell cmd list_quotas when not enable quota
> ----------------------------------------------------------------
>
> Key: HBASE-13987
> URL: https://issues.apache.org/jira/browse/HBASE-13987
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Minor
> Attachments: HBASE-13987.patch
>
>
> When not enable quota, use shell cmd list_quotas will get result as belows:
> hbase(main):008:0> list_quotas
> OWNER QUOTAS
>
>
> ERROR: Unknown table hbase:quota!
> It is confuse if user doesn't know quotas are stored in hbase:quota. I add
> check isQuotaEnabled before scan the table hbase:quota. So it will return
> result "ERROR: quota support disabled", which is same with set_quota.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
