Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 18 Dec 2012 18:48:12 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12545605.1331177567659.24353.1355856492808@arcas>
In-Reply-To: <JIRA.12545605.1331177567659@arcas>
References: <JIRA.12545605.1331177567659@arcas>
Subject: [jira] [Updated] (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:all-tabpanel ]

Christopher Tubbs updated ACCUMULO-452:
---------------------------------------

    Fix Version/s:     (was: 1.5.0)
    
> Generalize locality groups
> --------------------------
>
>                 Key: ACCUMULO-452
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-452
>             Project: Accumulo
>          Issue Type: New Feature
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>         Attachments: PartitionerDesign.txt
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira