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 7697311E8B for ; Tue, 16 Sep 2014 20:13:34 +0000 (UTC) Received: (qmail 72552 invoked by uid 500); 16 Sep 2014 20:13:34 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 72514 invoked by uid 500); 16 Sep 2014 20:13:34 -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 72501 invoked by uid 99); 16 Sep 2014 20:13:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2014 20:13:34 +0000 Date: Tue, 16 Sep 2014 20:13:33 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3134) Add options for file selection and creation to compact command 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-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136120#comment-14136120 ] Keith Turner commented on ACCUMULO-3134: ---------------------------------------- bq. Since we can't predict what options everybody's custom compaction strategies will need, does it make sense to just accept a map for configuration? My thinking was that these options would leverage a specific compaction strategy built into accumulo. If the compact command had an option for specifying a general compaction strategy w/ option map, then that could be mutually exclusive w/ these options. I think this approach will be less cumbersome to use, while still allowing generalization thats more cumbersome. > Add options for file selection and creation to compact command > -------------------------------------------------------------- > > Key: ACCUMULO-3134 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3134 > Project: Accumulo > Issue Type: Improvement > Reporter: Keith Turner > Fix For: 1.7.0 > > > Using a specialized compaction strategy and ACCUMULO-1798, options could be added to the shell's compact command to select specific files and configure the output file. > For example options like the following could be added for file selection. > * --sf-lt-size : select files less than a configurable size > * --sf-volume : selects files with a specified volume > * --sf-volume-re : selects files where the volume matches the specified regex > * --sf-name : selects files with a specfied name > * --sf-name-re : selects files where the name matches the specified regex > * --sf-compression : selects files with the specified compression type > * --sf-hdfs-block-size : selects files with a given hdfs block size > * --sf-rfile-data-block-size : selects file with a given rfile data block size > * --sf-rfile-index-block-size : selects file with a given rfile index block size > Options like the following could be added for file creation. > * --out-compression : creates a file with the specified compression type > * --out-hdfs-block-size : creates a file with a given hdfs block size > * --out-rfile-data-block-size : creates a file with a given rfile data block size > * --out-rfile-index-block-size : creates a file with a given rfile index block size -- This message was sent by Atlassian JIRA (v6.3.4#6332)