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 A7C24C77E for ; Mon, 10 Mar 2014 14:48:06 +0000 (UTC) Received: (qmail 45193 invoked by uid 500); 10 Mar 2014 14:48:03 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 44671 invoked by uid 500); 10 Mar 2014 14:48:02 -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 44658 invoked by uid 99); 10 Mar 2014 14:48:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 14:48:00 +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 (athena.apache.org: domain of yuzhihong@gmail.com designates 209.85.160.174 as permitted sender) Received: from [209.85.160.174] (HELO mail-yk0-f174.google.com) (209.85.160.174) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 14:47:56 +0000 Received: by mail-yk0-f174.google.com with SMTP id 20so19361499yks.5 for ; Mon, 10 Mar 2014 07:47:35 -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=dxt0j1yRmhVN+3FX1UXIOrgeOWmRJ9YDbUwZkO3gN3w=; b=Mz4KhMchMj21rA5l4fWgtZpKEKmltK8KOdJRYr9WBWd5AgJiypYlNQrSZh+069Ksf1 l/pvN+wFDEm2qxX2DuC2l8dHqFoDEPxc4ujG+zyEld0wwLff6EnE3vOx2RmQaN6aStel toH88ABEwQ6cG8J6PCDYVZQtwvGuCqgG1n/hFRu4BXVOrWp9Mce6kKPN2DSdxUbdZv6n 24K+ysRlrZqV2kJGStPMcyXFc/4KB+mcK54By7UWPIuRwbj96lw5oUoT+4qkFJfa5t5f I+8BJ0Uvnin97GbbQBkOC3EUeoFthizOQFecTKtTuC/mmlKmvDdp6uzvjl+eU9Wa7ft8 HZmw== MIME-Version: 1.0 X-Received: by 10.236.81.237 with SMTP id m73mr45249276yhe.29.1394462855635; Mon, 10 Mar 2014 07:47:35 -0700 (PDT) Received: by 10.170.79.86 with HTTP; Mon, 10 Mar 2014 07:47:35 -0700 (PDT) In-Reply-To: References: Date: Mon, 10 Mar 2014 07:47:35 -0700 Message-ID: Subject: Re: FuzzyRowFilter missing keys From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=20cf3011dba929a9ac04f441afba X-Virus-Checked: Checked by ClamAV on apache.org --20cf3011dba929a9ac04f441afba Content-Type: text/plain; charset=ISO-8859-1 Amit: Can you put your scenario in a unit test so that it is easier to pinpoint where the issue is ? Thanks On Mon, Mar 10, 2014 at 5:25 AM, Amit Sela wrote: > My table contains keys of this kind over an entire month but the scan > returns only for a some fo the days. > I have 2010101-20140131 but the scan returns only for: > 20140104, 20140110, 20140111, 20140118, 20140120, 20140125, 20140128 > > Using get or scan with no fuzzy filter works... > > > On Mon, Mar 10, 2014 at 1:59 PM, Bharath Vissapragada < > bharathv@cloudera.com > > wrote: > > > Is it because you fixed "_US_product1___" part of the key? From your > > definition of filter you should get as output all keys of form > > "yyyyMMdd_US_product1___". > > can you share a key thats of this format and missing in the output? > > > > > > On Mon, Mar 10, 2014 at 3:38 PM, Amit Sela wrote: > > > > > Hi all, > > > I'm using HBase 0.94.12 + Hadoop 1.0.4. > > > Trying to use FuzzyRowFilter looks like it's missing keys in the scan. > > > > > > Row key structure: > > > yyyyMMdd_Country_Product_Category1_Category2_ > > > Where the date is mandatory and all other fields may be "". > > > Examples: > > > 20140101_US_product1___ > > > 20140102__product1_bla__ > > > 20140103_____ > > > > > > Supplying the filter with row key: > > > \x00\x00\x00\x00\x00\x00\x00\x00_US_product1___ > > > and fuzzy info: > > > {1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} > > > > > > Over a range of a month, although the key exists for every day in the > > > month, I get result only for some of the days. > > > > > > I tried it on another table and the same happens, I'll mention that > both > > > tables have keys that start with yyyyMMdd. > > > > > > Anyone had a similar issue before ? I saw something in the mailing list > > > archives but no results there... > > > > > > Thanks, > > > Amit. > > > > > > > > > > > -- > > Bharath Vissapragada > > > > > --20cf3011dba929a9ac04f441afba--