[jira] [Resolved] (ACCUMULO-452) Generalize locality groups

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

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

Christopher Tubbs resolved ACCUMULO-452.
----------------------------------------
    Resolution: Not A Problem

I haven't heard any users asking for this kind of thing in a long time. I think they've become comfortable with various ways to design their application data in the row and column family to get the locality and ordering they need, without this feature.

I'm closing this, but if it's still an issue, please open an issue on GitHub, where we now track issues: https://github.com/apache/accumulo/issues

> Generalize locality groups
> --------------------------
>
>                 Key: ACCUMULO-452
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-452
>             Project: Accumulo
>          Issue Type: New Feature
>            Reporter: Keith Turner
>            Priority: Major
>         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 was sent by Atlassian JIRA
(v7.6.3#76005)