Hi Abhishek, How are you determining its resulting in full table scan? One way to ascertain that filter got pushed down is to see how many tasks were launched for your query, with and without filter. One would expect lower # of splits (and thus tasks) for query having filter.
Thanks, Ashutosh On Sun, Dec 28, 2014 at 8:38 PM, Abhishek kumar <abhishekiit...@gmail.com> wrote: > Hi, > > I am using hive 0.14 which runs over hbase (having ~10 GB of data). I am > facing issues in terms of slowness when querying over Hbase. My query looks > like following: > > select * from table1 where id > 'zzzz'; (id is the row-key) > > As per the hive-code, id > 'zzz', is getting pushed to Hbase scanner as > 'startKey'. Now given there are no such rows-keys (id) which satisfies this > criteria, this query should be extremely fast. But hive is taking a lot of > time, looks like full hbase table scan. > Can someone let me know where am I wrong in understanding the whole thing? > > -- > Abhishek >
