Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com
 designates 209.85.216.41 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=WvD7AfFS9zeuiOOWMC6PxGNSuIBxY5CDedbvBqc4jCRXNQJaU4Cr5USOYIxxNpS1dG
         fM6LmLpKFlfJB1/M9iEWI5/ABhq8q0DHpq6WQKh/YLP6FMUvMpmoCQt3JTvVmhe0/v0d
         cEqlAmni75hyyLJo6lc8a1qIeRXKJo34PEeZI=
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: <4DCA5175.6050101@1and1.ro>
References: <27014.55362.qm@web59301.mail.re1.yahoo.com>
	<4DCA5175.6050101@1and1.ro>
Date: Wed, 11 May 2011 10:05:12 -0700
Message-ID: <BANLkTi=FgyQx7PYO-mZv96a1L-H12aXuFg@mail.gmail.com>
Subject: Re: HBase filtered scan problem
From: Stack <stack@duboce.net>
To: user@hbase.apache.org
Cc: Stefan Comanita <comanita.stefan@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, May 11, 2011 at 2:05 AM, Iulia Zidaru <iulia.zidaru@1and1.ro> wrote=
:
> =A0Hi,
> I'll try to rephrase the problem...
> We have a table where we add an empty value.(The same thing happen also i=
f
> we have a value).
> Afterward we put a value inside.(Same put, just other value). When scanni=
ng
> for empty values (first values inserted), the result is wrong because the
> filter gets called for both values (the empty which maches and the not em=
pty
> which doesn't match). The table has only one version. It looks like the h=
eap
> object in StoreScanner has both objects. Do you have any idea if this is =
a
> normal behavior and if we can avoid this somehow?
>

Both entries exist in the hbase server, yes.

The coordinates for both are the same?  If exactly the same
row/cf/qualifier/timestamp then its going to be hard to distingush
between the two entries.  The filter is probably not smart enough to
take insertion order into account.

St.Ack