[
https://issues.apache.org/jira/browse/HBASE-17516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020885#comment-16020885
]
Hudson commented on HBASE-17516:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-HBASE-14614 #244 (See
[https://builds.apache.org/job/HBase-HBASE-14614/244/])
HBASE-17516 Correctly handle case where table and NS quotas both apply (elserj:
rev f031b69969003b7b33111312060a73858bada319)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/quotas/TestQuotaStatusRPCs.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/QuotaObserverChore.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/quotas/TestSpaceQuotas.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/quotas/TestQuotaObserverChoreWithMiniCluster.java
> Table quota not taking precedence over namespace quota
> ------------------------------------------------------
>
> Key: HBASE-17516
> URL: https://issues.apache.org/jira/browse/HBASE-17516
> Project: HBase
> Issue Type: Sub-task
> Reporter: Romil Choksi
> Assignee: Josh Elser
> Fix For: HBASE-16961
>
> Attachments: HBASE-17516.001.patch, HBASE-17516.002.HBASE-16961.patch
>
>
> [~romil.choksi] found a bug in the current patch-set where a more restrictive
> table quota did not take priority over a less-restrictive namespace quota.
> Turns out some of the logic to handle this case was incorrect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
