Mailing-List: contact accumulo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: accumulo-dev@incubator.apache.org
Date: Thu, 8 Mar 2012 03:35:00 +0000 (UTC)
From: "Keith Turner (Commented) (JIRA)" <jira@apache.org>
To: accumulo-dev@incubator.apache.org
Message-ID: 
 <790539797.37698.1331177700488.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1247235193.37697.1331177585736.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (ACCUMULO-452) Generalize locality groups
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Keith Turner commented on ACCUMULO-452:
---------------------------------------

I will put together an initial design document and post it for review.  


> Generalize locality groups
> --------------------------
>
>                 Key: ACCUMULO-452
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-452
>             Project: Accumulo
>          Issue Type: New Feature
>            Reporter: Keith Turner
>             Fix For: 1.5.0
>
>
> Locality groups are a neat feature, but there is no reason to limit partitioning to column families.  Data could be partitioned based on any criteria.  For example if a user is interested in querying recent data and ageing off old data partitioning locality groups based in timestamp would be useful.  This could be accomplished by letting users specify a partitioner plugin that is used at compaction and scan time.  Scans would need an ability to pass options to the partitioner.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira