You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2013/10/23 20:29:43 UTC
[jira] [Updated] (ACCUMULO-1802) use case for future
configurability of major compactions
[ https://issues.apache.org/jira/browse/ACCUMULO-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Turner updated ACCUMULO-1802:
-----------------------------------
Issue Type: New Feature (was: Sub-task)
Parent: (was: ACCUMULO-1451)
> use case for future configurability of major compactions
> --------------------------------------------------------
>
> Key: ACCUMULO-1802
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1802
> Project: Accumulo
> Issue Type: New Feature
> Components: tserver
> Reporter: Eric Newton
> Fix For: 1.7.0
>
>
> The default compaction strategy has a tendency to put the oldest data in the largest files. This leads to a lot of work when it is time to age off data.
> One could imaging a compaction strategy that would split data into separate files based on the timestamp. Additionally, if the min/max timestamps for a file were known, old data could be aged off by deleting whole files.
> Augment the configurable compaction strategy to support multiple output files, and saving/using extra metadata in each file.
--
This message was sent by Atlassian JIRA
(v6.1#6144)