problems with HBASE storage plugin

I am not able to get hbase storage plugin to work . HIVE storage plugin is working good though. From hbase I can see the tables and access them fine. The plugin in I am using is : { "type": "hbase", "config": { "hbase.zookeeper.quorum": "hadoop1,hadoop2,hadoop3", "hbase.zoo

RE: WELCOME to user@drill.apache.org

Hi Khurram the hive plugin is working now . I used the following configuration { "type": "hive", "configProps": { "hive.metastore.uris": "thrift://hadoop2:9083", "hive.metastore.sasl.enabled": "false", "hive.metastore.warehouse.dir": "/tmp/drill_hive_wh", "fs.default.name": "

cant select from hive table

Hi My hive storage plugin is working and I can see the hive tables but I can’t select from them ,please advise apache drill (hive.default)> show tables; +--++ | TABLE_SCHEMA | TABLE_NAME | +--++ | hive.default | test | +--+---

RE: WELCOME to user@drill.apache.org

I am using apache drill 1.16 , its not letting me use this plugin .. I get an error "Please retry: Error while creating / updating storage : null" Why ? Changed it as per your instructions but still no good { "type": "hive", "configProps": { "hive.metastore.uris": "thrift://hadoop2:90

RE: cant select from hive table

As you can see , the show table command sees the table but select command cant find it . pache drill (hive.default)> show tables; +--++ | TABLE_SCHEMA | TABLE_NAME | +--++ | hive.default | test | +--++ 1 row selected (0

Re: cant select from hive table

Default is keyword, use it back-ticks (select * from hive.`default`.test). > On May 24, 2019, at 10:59 PM, Ahmad, Sami wrote: > > As you can see , the show table command sees the table but select command > cant find it . > > pache drill (hive.default)> show tables; > +--+--

strange planning error

I have a bunch of data that I want to group up and look at the counts. In order to get a row number for plotting, I tried a window function. The data consists of about 7,2 million rows accessed via a view[1]. The columns are pretty much all untyped[2]. This query works great: *with * *t0 as (*

Re: strange planning error

The changing of the column order in the SELECT should not materially affect the planning, so this does look like a bug. I was able to repro it with a simpler example (without the group-by): select row_number() over (order by department_id desc) r, department_id from (select

Re: Drill Meetup @ Santa Clara (Wednesday)

Thank you so much for sharing this as off-site people like me would be benefited :). Just a quick suggestion can we create a tab “Drill talks and presentation” in Apache Drill website and share all the presentation links there . Allow folks to upload there talks/presentation. Even I have presented

Re: strange planning error

Good eye to spot the issue with redundant ordering. No, I don't need both. The reason I wound up with two is due to my building and rebuilding the query many times. Essentially, a cut and paste error led to that. This is good news is it is much less likely that most (sensible) users run into this.