hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17794) Remove lingering "violation" in favor of the accurate "snapshot"
Date Mon, 20 Mar 2017 19:13:41 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Josh Elser updated HBASE-17794:
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Pushed to the feature branch. Thanks, Ted!

> Remove lingering "violation" in favor of the accurate "snapshot"
> ----------------------------------------------------------------
>                 Key: HBASE-17794
>                 URL: https://issues.apache.org/jira/browse/HBASE-17794
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Trivial
>             Fix For: HBASE-16961
>         Attachments: HBASE-17794.001.HBASE-16961.patch
> Previously, quota violations used to be stored in the quota table. Eventually, I realized
that I needed to actually persist the utilization of each table/NS, not just the violation
> I know there are cases in the code where "violation" is incorrectly describing things
(it should be "snapshot"). Clean these up for clarity.

This message was sent by Atlassian JIRA

View raw message