You can always remove the NOT clause by changing the statement, but I'm wondering what your use case really is. HBase doesn't have secondary indexes so, unless you are doing a short-ish scan (let's say a million rows), it means you want to do a full table scan and that doesn't scale.
J-D On Tue, Sep 17, 2013 at 1:34 AM, Ashwin Jain <ashvyn.j...@gmail.com> wrote: > Hello All, > > Does HBase not support an SQL NOT operator on complex filters? I would like > to filter out whatever matches a complex nested filter. > > my use case is to parse a query like this(below) and build a HBase filter > from it. > (field1=value1 AND NOT ((field2=value2 OR field3=value3) AND > field4=value4)) > > How to go about this , any ideas? What will be a better approach - > implement a custom filter that excludes a row qualified by another filter > or to convert input query into an opposite query. > > Thanks, > Ashwin >
