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 25A3410AEF for ; Thu, 22 Aug 2013 00:38:46 +0000 (UTC) Received: (qmail 43484 invoked by uid 500); 22 Aug 2013 00:38:46 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 43448 invoked by uid 500); 22 Aug 2013 00:38:45 -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 43440 invoked by uid 99); 22 Aug 2013 00:38:45 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Aug 2013 00:38:45 +0000 Received: from localhost (HELO mail-la0-f43.google.com) (127.0.0.1) (smtp-auth username vines, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Aug 2013 00:38:45 +0000 Received: by mail-la0-f43.google.com with SMTP id ep20so888646lab.2 for ; Wed, 21 Aug 2013 17:38:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=fR+XywfeAKMJMnYJVMOC98Ch55fZD6A9HxGThC75Io4=; b=MoztZhIbtiHag3hA9ogooHgUQPSKW+27RSy9dyCxMbtgf21ifzGeDAFuCYNuvdRbIQ 7aWdIi6AlPOFd6cES7coS0ZZErs8ca8An6GIbHvnv9i757ovTBfESLkYWUFp2ItF2Nfq aMpDEpWoG12bCikSLSh+d1nBmYzPRe1w9PWiBDYK+2gm9nifoLRuoTlYEPsuY7qa6cBz ID7SliZH/SLX69f4nakvsnPYqIyLybZ16dkxkRajZYLatUirpXr2YpBDouOB0akV1PvX iZCfyjwiNMaUc0C7qhux3yCXTztn7a9IrgRIeUCZFKV7z56rcuN31yfCKfKdh4brFva6 DTbg== X-Received: by 10.152.8.115 with SMTP id q19mr8215569laa.16.1377131923646; Wed, 21 Aug 2013 17:38:43 -0700 (PDT) MIME-Version: 1.0 Reply-To: vines@apache.org Received: by 10.114.177.97 with HTTP; Wed, 21 Aug 2013 17:38:03 -0700 (PDT) In-Reply-To: References: From: John Vines Date: Wed, 21 Aug 2013 20:38:03 -0400 Message-ID: Subject: Re: Filtering on column qualifier To: "user@accumulo.apache.org" Content-Type: multipart/alternative; boundary=001a11c34f5c1e311204e47e8314 --001a11c34f5c1e311204e47e8314 Content-Type: text/plain; charset=ISO-8859-1 Nope, it's just a custom Filter, which is a type of iterator. You can attach iterators to run on a scanner, you just need to make sure you deploy the jar with the custom iterator to all of the tservers. On Wed, Aug 21, 2013 at 7:58 PM, Slater, David M. wrote: > Would this require extending the BatchScanner as well to make use of the > extended ColumnQualifierFilter, or could this be done with an unmodified > BatchScanner?**** > > ** ** > > *From:* John Vines [mailto:vines@apache.org] > *Sent:* Wednesday, August 21, 2013 10:49 AM > *To:* user@accumulo.apache.org > *Subject:* Re: Filtering on column qualifier**** > > ** ** > > There's no way to extend the ColumnQualietyFilter via configuration, but > it sounds like you are on top of it. You just need to extend the class, > possibly copy a bit of code, and change the equality check to a compareTo > after converting the Strings to Doubles.**** > > ** ** > > On Wed, Aug 21, 2013 at 10:00 AM, Marc Reichman < > mreichman@pixelforensics.com> wrote:**** > > I have some data stored in Accumulo with some scores stored as column > qualifiers (there was an older thread about this). I would like to find a > way to do thresholding when retrieving the data without retrieving it all > and then manually filtering out items below my threshold.**** > > ** ** > > I know I can "fetch" column qualifiers which are exact.**** > > ** ** > > I've seen the ColumnQualifierFilter, which I assume is what's in play when > I fetch qualifiers. Is there a reasonable pattern to extend this and try to > use it as a scan iterator so I can do things like "greater than" a value > which will be interpreted as a Double vs. the string equality going on now? > **** > > ** ** > > Thanks,**** > > Marc**** > > ** ** > --001a11c34f5c1e311204e47e8314 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Nope, it's just a custom Filter, which is a type of it= erator. You can attach iterators to run on a scanner, you just need to make= sure you deploy the jar with the custom iterator to all of the tservers.


On Wed, Aug 2= 1, 2013 at 7:58 PM, Slater, David M. <David.Slater@jhuapl.edu>= ; wrote:

Would this re= quire extending the BatchScanner as well to make use of the extended Column= QualifierFilter, or could this be done with an unmodified BatchScanner?<= /u>

=A0<= /p>

From: John = Vines [mailto:vines@a= pache.org]
Sent: Wednesday, August 21, 2013 10:49 AM
To: user@accumulo.apache.org<= /a>
Subject: Re: Filtering on column qualifier

=A0

There's no way to extend the ColumnQualietyFilter v= ia configuration, but it sounds like you are on top of it. You just need to= extend the class, possibly copy a bit of code, and change the equality che= ck to a compareTo after converting the Strings to Doubles.

=A0=

On Wed, Aug 21, 2013 at 10:00 AM, Ma= rc Reichman <mreichman@pixelforensics.com> wrote:

I have some data stored in Accumulo with some s= cores stored as column qualifiers (there was an older thread about this). I= would like to find a way to do thresholding when retrieving the data witho= ut retrieving it all and then manually filtering out items below my thresho= ld.

=A0

I know I can "fetch" column qualifiers which are exact.

=A0

I've seen the ColumnQualifierFilter, which I ass= ume is what's in play when I fetch qualifiers. Is there a reasonable pa= ttern to extend this and try to use it as a scan iterator so I can do thing= s like "greater than" a value which will be interpreted as a Doub= le vs. the string equality going on now?

=A0

Thanks,

M= arc

=A0=


--001a11c34f5c1e311204e47e8314--