Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 23 Oct 2012 06:51:14 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <513206705.14860.1350975074057.JavaMail.jiratomcat@arcas>
In-Reply-To: <372407485.74306.1342672174956.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HBASE-6428) Pluggable Compaction policies
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl commented on HBASE-6428:
--------------------------------------

Hmm... This actually would be much simpler if the entire Compactor class could be pluggable; along with some refactoring of that class into an extensible interface.
I guess that's what HBASE-5334 has in mind.

                
> Pluggable Compaction policies
> -----------------------------
>
>                 Key: HBASE-6428
>                 URL: https://issues.apache.org/jira/browse/HBASE-6428
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Lars Hofhansl
>
> For some usecases is useful to allow more control over how KVs get compacted.
> For example one could envision storing old versions of a KV separate HFiles, which then rarely have to be touched/cached by queries querying for new data.
> In addition these date ranged HFile can be easily used for backups while maintaining historical data.
> This would be a major change, allowing compactions to provide multiple targets (not just a filter).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira