Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <188734536.1220638964574.JavaMail.jira@brutus>
Date: Fri, 5 Sep 2008 11:22:44 -0700 (PDT)
From: "Jonathan Gray (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-871) Major configuration periodicity
 should be specifyable at the column family level, not cluster wide
In-Reply-To: <703707469.1220564504297.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628690#action_12628690 ] 

Jonathan Gray commented on HBASE-871:
-------------------------------------

Confirmed that patch applies to 0.2 branch and trunk

> Major configuration periodicity should be specifyable at the column family level, not cluster wide
> --------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-871
>                 URL: https://issues.apache.org/jira/browse/HBASE-871
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Jonathan Gray
>         Attachments: hbase-871-v1.patch
>
>
> jon gray has a table of ten rows and a couple of columns that is constantly being updated.  Has max versions of 2.  This table is growing fast because all versions written are kept until a major compaction.  The way this table is being used is different than that of others.  Would be good if he could have major compactions run more often than the default once a day.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.