hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: HBase filtered scan problem
Date Wed, 11 May 2011 17:05:12 GMT
On Wed, May 11, 2011 at 2:05 AM, Iulia Zidaru <iulia.zidaru@1and1.ro> wrote:
>  Hi,
> I'll try to rephrase the problem...
> We have a table where we add an empty value.(The same thing happen also if
> we have a value).
> Afterward we put a value inside.(Same put, just other value). When scanning
> 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 empty
> which doesn't match). The table has only one version. It looks like the heap
> 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.


View raw message