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 445D6D1D1 for ; Wed, 17 Oct 2012 06:33:16 +0000 (UTC) Received: (qmail 66332 invoked by uid 500); 17 Oct 2012 06:33:16 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 66155 invoked by uid 500); 17 Oct 2012 06:33:11 -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 66127 invoked by uid 99); 17 Oct 2012 06:33:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2012 06:33:10 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ctubbsii@gmail.com designates 209.85.223.169 as permitted sender) Received: from [209.85.223.169] (HELO mail-ie0-f169.google.com) (209.85.223.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2012 06:33:06 +0000 Received: by mail-ie0-f169.google.com with SMTP id 10so13975903ied.0 for ; Tue, 16 Oct 2012 23:32:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=6l8vSYDfhRh63U47skB0cUiso/9EScHcsnUnz7mmjzw=; b=iNreR+hulKSxQAfSF1Pks56GcxaXUlFXcAxxmmt8s+KEBbvuWpODpr2c5gXvYb4PUe x5OZdYEw7cq+jzQS3MPFs2hlFEOcsgvCuQ962HO82aM4N32zD8CT/Fl3bviVlJK1M8dj IKV3L0VVX4xmIAqbABccS7rvM3vZZHgqqorfF9LpaZIDW05zisc86YjKGL3O91rH43uQ urprTRINkyk0Aax5gy16BtVzs8ocEeIQ/OGUU375a1L42wvNIvc2XHOrXczyo4HbGjo8 DSlFc0yLSsie4YXxCef9q/rGbl4NlGDjwuANbeoAjEtVhn404whqPUTVYPuKtS8M5PBt d/0A== MIME-Version: 1.0 Received: by 10.50.41.132 with SMTP id f4mr587617igl.39.1350455565191; Tue, 16 Oct 2012 23:32:45 -0700 (PDT) Received: by 10.64.61.70 with HTTP; Tue, 16 Oct 2012 23:32:45 -0700 (PDT) In-Reply-To: References: <8981F843EE8088488986AB76F63A790313E02090@endeavour.eoir.com> Date: Wed, 17 Oct 2012 02:32:45 -0400 Message-ID: Subject: Re: Concurrent updates From: Christopher Tubbs To: user@accumulo.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org If you're going to only do aggregation at the scan scope, you'd probably want to make sure you don't have the versioning iterator turned on for minc and majc scopes. Otherwise, you're scans may look different over time between initial ingest and later, when the data has been compacted on disk. -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Tue, Oct 16, 2012 at 9:15 PM, Mike Drob wrote: > One option is to only set the aggregation for scan scope, and then you can > programatically choose which one you need. > > > On Tue, Oct 16, 2012 at 9:03 PM, David Medinets > wrote: >> >> On Tue, Oct 16, 2012 at 6:19 PM, Eric Newton >> wrote: >> > Accumulo also supports a very specific kind of update which is very >> > helpful in the case of sums and aggregates. >> >> I'll ask the obvious follow-up question. If two kinds of sums are >> needed (i.e., summing by day and week), would an event need to be >> written to two tables? > >