Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 22 Oct 2013 19:16:45 +0000 (UTC)
From: "Billie Rinaldi (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12675093.1382466277560.105720.1382469405032@arcas>
In-Reply-To: <JIRA.12675093.1382466277560@arcas>
References: <JIRA.12675093.1382466277560@arcas>
Subject: [jira] [Commented] (ACCUMULO-1802) use case for future
 configurability of major compactions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Billie Rinaldi commented on ACCUMULO-1802:
------------------------------------------

One could also imagine matching a reading strategy with a compaction strategy, to allow skipping of entire files based on file metadata when reading.

> use case for future configurability of major compactions
> --------------------------------------------------------
>
>                 Key: ACCUMULO-1802
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1802
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: tserver
>            Reporter: Eric Newton
>             Fix For: 1.6.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)