Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 625EDF329 for ; Tue, 9 Apr 2013 17:57:55 +0000 (UTC) Received: (qmail 82721 invoked by uid 500); 9 Apr 2013 17:57:53 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 82660 invoked by uid 500); 9 Apr 2013 17:57:52 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 82651 invoked by uid 99); 9 Apr 2013 17:57:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 17:57:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of taton@wibidata.com designates 209.85.219.53 as permitted sender) Received: from [209.85.219.53] (HELO mail-oa0-f53.google.com) (209.85.219.53) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 17:57:47 +0000 Received: by mail-oa0-f53.google.com with SMTP id m17so7608446oag.40 for ; Tue, 09 Apr 2013 10:57:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wibidata.com; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=XPDulan0XU9I6pKT95UC+8U6yHa7rAIarRojJwVTV58=; b=DtFXiv6/G47/SKMHL0ubJtamwaS0qXBT5F6J/KliSeRXN1OOhCDaOWH9h9wjQWQAuM NY+32/CNM3Q2NRNbqej7biMUwAkaLaD3rP+kJ3F4Ev4iFTdSm/tffTb+/2uN6P+OuAyq V3+e6/i4LDKE/z0Iyjcsys8nGUdgrqBVqqp3Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=XPDulan0XU9I6pKT95UC+8U6yHa7rAIarRojJwVTV58=; b=DFfaXc6AzZOo8j+c9sFFF5IbIhlPqFoOPA+cOQEs6sbxy7lWTPTND+8YlO0o8wnUrI lRHD+vGG55qwJSScxJZZiCmzDlMb8HxXv8G+KQyR0UZzIiqTCwiiUgsOTPoFQMorC1ds IlyCjeqNKEEqHh1v7FyzqCiM0MMT2jD9GKb49dnYAYHtmlBiIO+2OD9O++MDYYvYKnyc yAvziB15IhSYkrcB0IB4daxA0cMTdyMs5YpppDDSjTVwiuzf0F2j+Q37zwgP15w9eUiO WFmsngK14b16YdmLMv3h9gW+dmKIQtXCJPlRvk1+ZTR3LhAcRqLcSydUJ5nIOt7liu9R 1ngg== MIME-Version: 1.0 X-Received: by 10.60.50.102 with SMTP id b6mr19035480oeo.46.1365530245028; Tue, 09 Apr 2013 10:57:25 -0700 (PDT) Received: by 10.60.60.234 with HTTP; Tue, 9 Apr 2013 10:57:24 -0700 (PDT) In-Reply-To: References: <1365200920.10142.YahooMailNeo@web140606.mail.bf1.yahoo.com> Date: Tue, 9 Apr 2013 10:57:24 -0700 Message-ID: Subject: Re: Interactions between max versions and filters From: Christophe Taton To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001a11c1d64c2f6be104d9f14921 X-Gm-Message-State: ALoCoQnoxTvlZP65tjPvwMbw8Qpan45hunk6b7wh8SgLx6ZDllDTWJ8fWYHQ/bff84wo1Ga+as/b X-Virus-Checked: Checked by ClamAV on apache.org --001a11c1d64c2f6be104d9f14921 Content-Type: text/plain; charset=UTF-8 Hi, Thanks for all your answers, that was very helpful. It appears we were using the non-intended behavior of the ColumnPaginationFilter. I now understand that: - max versions applies post-filtering. - ColumnPaginationFilter forces max-versions to 1 (and so does ColumnCountGetFilter). >From some experiments, the offset of the ColumnPaginationFilter appears fairly inefficient, and it seems I will always want it to be 0. Instead, I'd combine the ColumnPaginationFilter with a ColumnRangeFilter that sets a low bound on columns. C. On Sat, Apr 6, 2013 at 12:55 PM, Varun Sharma wrote: > Looking at the JIRA, I added a couple of tests to the 0.94 version for > checking deleting versions etc. - if u look at the 0.94 patch. > > Perhaps, we should carry over those tests to trunk - my bad on not adding > those tests... > > On Sat, Apr 6, 2013 at 7:10 AM, Ted Yu wrote: > > > Looking at > > > https://issues.apache.org/jira/secure/attachment/12550741/5257-trunk-v2.txt > > , > > TestFilter#testColumnPaginationFilter() was modified but no new test was > > added. > > > > I think Christophe is in better position to suggest what additional test > > should be added based on his use case. > > > > Cheers > > > > > > On Sat, Apr 6, 2013 at 6:58 AM, Jean-Marc Spaggiari < > > jean-marc@spaggiari.org > > > wrote: > > > > > Ted, should we have such test in the test suite? If so, should a JIRA > > > be opened for that? > > > > > > JM > > > > > > 2013/4/6 Ted Yu : > > > > Christophe: > > > > HBASE-5257 has been integrated into 0.94 > > > > Can you try 0.94.6.1 to see if the problem is solved ? > > > > > > > > Writing a unit test probably is the easiest way for validation. > > > > > > > > Thanks > > > > > > > > > > > > On Fri, Apr 5, 2013 at 5:25 PM, Varun Sharma > > > wrote: > > > > > > > >> HBASE 5257 is probably what lars is talking about - that fixed a bug > > > with > > > >> version tracking on ColumnPaginatinoFilter - there is a patch for > > 0.92, > > > >> 0.94 and 0.96 but not for the cdh versions... > > > >> > > > >> On Fri, Apr 5, 2013 at 3:28 PM, lars hofhansl > > wrote: > > > >> > > > >> > Normally Filters are evaluated before the version counting. There > > was > > > >> some > > > >> > issue that was fixed recently that changed this behavior > > specifically > > > for > > > >> > ColumnPaginationFilters and friend... Lemme see if I can find > that. > > > >> > > > > >> > > > > >> > > > > >> > ________________________________ > > > >> > From: Stack > > > >> > To: Hbase-User > > > >> > Sent: Friday, April 5, 2013 3:05 PM > > > >> > Subject: Re: Interactions between max versions and filters > > > >> > > > > >> > On Fri, Apr 5, 2013 at 11:19 AM, Christophe Taton < > > taton@wibidata.com > > > >> > >wrote: > > > >> > > > > >> > > Hi, > > > >> > > > > > >> > > Is there an explicit specification of the behavior of max > versions > > > (set > > > >> > in > > > >> > > a get/scan) when combined with filters? > > > >> > > From my experiments (with 0.92 CDH4.1.2), the max versions is > > > applied > > > >> in > > > >> > a > > > >> > > way that is neither pre-filtering nor post-filtering. > > > >> > > In particular, I am currently playing with the > > > ColumnPaginationFilter, > > > >> > and > > > >> > > I am not entirely certain I understand the intended/expected > > > behavior. > > > >> > > I also did not find an explicit specification in the reference > > user > > > >> guide > > > >> > > nor in the API javadoc. > > > >> > > > > > >> > > > > >> > > > > >> > Hey Christophe: > > > >> > > > > >> > Sounds like a bug. My understanding is that the regardless of > > > filters, > > > >> max > > > >> > versions should be respected (Yes, we should have a specification > > but > > > we > > > >> do > > > >> > not have one here). > > > >> > > > > >> > Yours, > > > >> > St.Ack > > > >> > > > > >> > > > > > > --001a11c1d64c2f6be104d9f14921--