RE: Filters for non-Java clients?

[Greg Cottman <gr...@quest.com>]

Oops.  My bad.  Looking at http://wiki.apache.org/hadoop/Hbase/Stargate and the Scanner type definition does include a "filter" element. <blush>  It may be worth mentioning the filter support in the section on Scanner creation, even if you attach a caveat about needing to be brave.

I'll have a look at ScannerModel in the Java API.  Thanks Andy.

Cheers,
Greg.

-----Original Message-----
From: Andrew Purtell [mailto:apurtell@apache.org] 
Sent: Tuesday, 26 July 2011 2:42 AM
To: user@hbase.apache.org
Subject: Re: Filters for non-Java clients?

The REST API has filter support.

Strictly speaking the representation is multilanguage, but only the Java API -- the ScannerModel class, ScannerModel.stringifyFilter -- has support for converting a Java filter tree into a JSON encoded representation of same. However you could do this in Java once to obtain the filter string and then use that string as-is with the C++ client.
 
Best regards,


   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)


----- Original Message -----
> From: Greg Cottman <gr...@quest.com>
> To: "user@hbase.apache.org" <us...@hbase.apache.org>
> Cc: 
> Sent: Sunday, July 24, 2011 10:20 PM
> Subject: Filters for non-Java clients?
> 
> 
> We are using the REST interface because we have a C++ client, but get 
> performance complaints arising from the fact that we have to fetch the entire 
> table for any query.
> 
> Is anyone considering exposing the Java Filter implementation for scanners in 
> either the REST or Thrift APIs?  If so, is there a timeline?
> 
> It wouldn't have to be as rich as the 42 implementations of the Java Filter 
> interface.  Just being able to do a simple range scan on one or more columns 
> would be a really exciting prospect.  :-)
> 
> Cheers,
> Greg.
> 
> 
> Greg Cottman
> Technical Architect, Cloud Databases
> Quest Software, Melbourne
> Tel: +61 3 9811 8057
> Greg.Cottman@quest.com
>