hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From schnitzi <mark.schnitz...@fastsearch.com>
Subject Re: ColumnValueFilter issue
Date Fri, 19 Jun 2009 05:50:21 GMT

Isn't it always the way?  As soon as you post a question to a forum, you
figure out the answer...

For the benefit of future generations, the first 'columns' parameter to
getScanner(...) needs to include the column you are comparing on, if you're
using a ColumnValueFilter.  I thought you would only need to include the
columns you were subsequently interested in seeing in the results.

It would be nice to see an exception generated for this, instead of just no

schnitzi wrote:
> I'm using HBase 0.19.3, and seeing some unusual behavior around
> ColumnValueFilter.  When I do this...
>     Scanner scanner = myTable.getScanner(COLUMN1, startKey);
> ...I get three results.  But if I do...
>     Scanner scanner = myTable.getScanner(COLUMN1, startKey, new
> ColumnValueFilter(COL1,
>                 ColumnValueFilter.CompareOp.NOT_EQUAL,
> Bytes.toBytes("foo")));
> ...I get no results, where I would expect three.  But even if I change
>     Scanner scanner = myTable.getScanner(COLUMN1, startKey, new
> ColumnValueFilter(COL1,
>                 ColumnValueFilter.CompareOp.EQUAL, Bytes.toBytes("foo")));
> ...I get no results.  Is there something about ColumnValueFilter I'm not
> understanding?  I would expect either EQUAL or NOT_EQUAL to return
> *something*...
> Thanks
> Mark

View this message in context: http://www.nabble.com/ColumnValueFilter-issue-tp24105833p24105876.html
Sent from the HBase User mailing list archive at Nabble.com.

View raw message