Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B779410C63 for ; Mon, 21 Oct 2013 18:14:50 +0000 (UTC) Received: (qmail 14699 invoked by uid 500); 21 Oct 2013 18:14:47 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 14555 invoked by uid 500); 21 Oct 2013 18:14:44 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 14474 invoked by uid 99); 21 Oct 2013 18:14:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Oct 2013 18:14:42 +0000 Date: Mon, 21 Oct 2013 18:14:42 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (ACCUMULO-1451) Make Compaction triggers extensible MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800902#comment-13800902 ] Keith Turner edited comment on ACCUMULO-1451 at 10/21/13 6:13 PM: ------------------------------------------------------------------ [~ecn] and I were just discussing this. We were talking about limiting the scope of this for 1.6 w/o precluding useful changes that we are aware of for later versions. Some changes we disccused for 1.6. * Move chop logic completely outside of compaction strategy (So user can not break merges). Also do not invoke compaction strategy for user initiated compactions. * Move delete propagation logic outside of compaction strategy * Gear APIs for 1.6 twoards 1 output file, but structure current API such that support multiple files can be added in future w/o breaking compaction strategies written for 1.6. * Return a single list of output files, dropping passes. The implementation may still do multiple passes, but the strategy will not have control over this. * Push allowing users to specify a compaction strategy (and config for the strategy) on a user initiated compaction to a later release. was (Author: kturner): @ecn and I were just discussing this. We were talking about limiting the scope of this for 1.6 w/o precluding useful changes that we are aware of for later versions. Some changes we disccused for 1.6. * Move chop logic completely outside of compaction strategy (So user can not break merges). Also do not invoke compaction strategy for user initiated compactions. * Move delete propagation logic outside of compaction strategy * Gear APIs for 1.6 twoards 1 output file, but structure current API such that support multiple files can be added in future w/o breaking compaction strategies written for 1.6. * Return a single list of output files, dropping passes. The implementation may still do multiple passes, but the strategy will not have control over this. * Push allowing users to specify a compaction strategy (and config for the strategy) on a user initiated compaction to a later release. > Make Compaction triggers extensible > ----------------------------------- > > Key: ACCUMULO-1451 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1451 > Project: Accumulo > Issue Type: Improvement > Components: tserver > Affects Versions: 1.5.0 > Reporter: Mike Drob > Assignee: Eric Newton > > It would be nice to have extensible triggers for determining when to run compactions. This can facilitate better ways to age-off data, for example. -- This message was sent by Atlassian JIRA (v6.1#6144)