Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EF63C9998 for ; Wed, 23 May 2012 20:39:41 +0000 (UTC) Received: (qmail 81988 invoked by uid 500); 23 May 2012 20:39:41 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 81920 invoked by uid 500); 23 May 2012 20:39:41 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 81899 invoked by uid 99); 23 May 2012 20:39:41 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2012 20:39:41 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 524CA14282A for ; Wed, 23 May 2012 20:39:41 +0000 (UTC) Date: Wed, 23 May 2012 20:39:41 +0000 (UTC) From: "Keith Turner (JIRA)" To: dev@accumulo.apache.org Message-ID: <451202753.13100.1337805581339.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (ACCUMULO-420) Allow per compaction iterator settings 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-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281890#comment-13281890 ] Keith Turner commented on ACCUMULO-420: --------------------------------------- Adding this to the API should be fairly simple. Thinking of simply adding the following to TableOperations {code} public void compact(String tableName, Text start, Text end, List iterators, boolean flush, boolean wait) {code} However making this functionality available from the shell does not seem so simple. Billie and I discussed this today and came up with some initial thoughts, but did not decide on anything. * Allow arguments to the compact command like ={ =). For each iterator argument given to the compact command it would then prompt you for options. This does not seem great for writing scripts that initiate compactions. * Repurpose the setscaniter command to allow creating an iterator profile in the shell. Then a scan or compact command could reference this iterator profile. This way iterators configured on the shell are only used if explicitly requested. This also does not seem great for scripting compactions. * Compact command could take an argument that is a complex expression that encapsulates iterators and their options. This is great for scripting but not so good for interactive use. > Allow per compaction iterator settings > -------------------------------------- > > Key: ACCUMULO-420 > URL: https://issues.apache.org/jira/browse/ACCUMULO-420 > Project: Accumulo > Issue Type: New Feature > Reporter: Keith Turner > Assignee: Sapan Shah > Fix For: 1.5.0 > > > It may be useful to allow the compact command to specify an iterator to be used for that compaction. For example if someone wanted to apply a filter once to a table, they could force a compaction with that filter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira