Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD29E10E93 for ; Fri, 22 Nov 2013 16:04:47 +0000 (UTC) Received: (qmail 71341 invoked by uid 500); 22 Nov 2013 16:04:47 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 71133 invoked by uid 500); 22 Nov 2013 16:04:47 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 71124 invoked by uid 99); 22 Nov 2013 16:04:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Nov 2013 16:04:47 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of wilhelm.von.cloud@accumulo.net does not designate 209.85.214.179 as permitted sender) Received: from [209.85.214.179] (HELO mail-ob0-f179.google.com) (209.85.214.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Nov 2013 16:04:40 +0000 Received: by mail-ob0-f179.google.com with SMTP id wm4so1481536obc.38 for ; Fri, 22 Nov 2013 08:04:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=7F8HKiTtxCNa1KjEWqX7HbbUqcOAkmspRc0p9jj+bhU=; b=IWDtE293OC6SJTU/rxnmjmvpWTY5sOKQG/hTEmjAjRSwpr3Hyfdf8GJbWoQBNoYfeC 1EFczZM9CfUQCnWXqBiaGuUCsqQXPtHoLbH5/auYPzz5PJW1JaxemiVVnjbgky5ozZvJ nVxq+ezlqts2dTDrtISqD0idulzQuK0P/n7I34A62hZ/fm7INMXCJcdDlSIch9ECLL7z ULAIgz5eETFxhPkwIXQaRXfyA/S4waS9jNFQHWzZMZLqlM+/C5CaA50wAjqsPXBSEI2u fMmmKgFdvK6zJGbmpyTSRiYh/zBI4bVVtkNitW4zRpZmLspvddUfx7WZ38lcVnmUgnoF Uthg== X-Gm-Message-State: ALoCoQnDFDjCwvjvdzCUDXPXfn0h8uGzeSqHlXrKnpKQHm4ZLXP1hcI7/XIBdtT6CSwhGWMVtCAh MIME-Version: 1.0 X-Received: by 10.60.65.227 with SMTP id a3mr11202609oet.13.1385136258545; Fri, 22 Nov 2013 08:04:18 -0800 (PST) Received: by 10.182.144.133 with HTTP; Fri, 22 Nov 2013 08:04:18 -0800 (PST) X-Originating-IP: [98.117.207.73] In-Reply-To: References: Date: Fri, 22 Nov 2013 11:04:18 -0500 Message-ID: Subject: Re: AgeOff Filter - Compaction needed? From: William Slacum To: user@accumulo.apache.org Content-Type: multipart/alternative; boundary=001a11c25700a8111004ebc62a27 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c25700a8111004ebc62a27 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Compaction will occur naturally as the table grows. If the data is old and the table is static, forcing a compaction via the shell is probably the easiest route. On Fri, Nov 22, 2013 at 10:58 AM, Slater, David M. wrote: > Hi, I would like to automatically ageoff old data; however my > understanding of AgeOff iterators is that they would require a compaction > or scan to take effect. For information that is in tablets that are no > longer being added to or scanned, the ageoff filter would not take effect= , > correct? > > > > Would I need to force a compaction or merge in order to remove those > records, or would it be better to write my own script to remove rows? (I= =92m > using 1.4 =96 is this behavior different in 1.5 or 1.6?) > > > > Thanks, > David > --001a11c25700a8111004ebc62a27 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Compaction will occur naturally as the table grows. If the= data is old and the table is static, forcing a compaction via the shell is= probably the easiest route.


On Fri, Nov 22, 2013 at 10:58 AM, Slater, David M. <David.Slater@jhu= apl.edu> wrote:

Hi, I would like to automatically ageoff old data; however my understan= ding of AgeOff iterators is that they would require a compaction or scan to= take effect. For information that is in tablets that are no longer being a= dded to or scanned, the ageoff filter would not take effect, correct?

=A0

Would I = need to force a compaction or merge in order to remove those records, or wo= uld it be better to write my own script to remove rows? (I=92m using 1.4 = =96 is this behavior different in 1.5 or 1.6?)

=A0

Thanks,<= br>David


--001a11c25700a8111004ebc62a27--