You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Kunal Khatua (JIRA)" <ji...@apache.org> on 2017/12/15 04:27:00 UTC

[jira] [Updated] (DRILL-6033) Using Drill Hive connection to query an Hbase table

     [ https://issues.apache.org/jira/browse/DRILL-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kunal Khatua updated DRILL-6033:
--------------------------------
    Fix Version/s: Future

> Using Drill Hive connection to query an Hbase table
> ---------------------------------------------------
>
>                 Key: DRILL-6033
>                 URL: https://issues.apache.org/jira/browse/DRILL-6033
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.11.0
>         Environment: 3 instances of Cloudera 5.10v , each one have a drillbit installed. Each machine has 24 vCPU.
>            Reporter: Dor
>              Labels: drill, hbase, hive
>             Fix For: Future
>
>
> Using Drill hive connection to query Hbase table.
> +*Following query *+
> select * from hive.mytable where key >= '0001:10:2017:0410:0000000000003157781'
> and key < '0001:10:2017:0410:0000000000003157782';
> +*What happened*+
> Failed with an error after timeout.
> It seems that the word 'key' didn't push down to hive from drill.
> +*What we also tried*+
> Same query in Drill over hbase takes less than a sec,
> In hue hive it takes few seconds
> +*Debug trail*+
> When you look in the sql profile of drill (using the web), you see a 
> table full scan for millions of records, while actually it was supposed to return
> 9 rows.
> Does Drill on top of hive is using the key to access only the relevant 
> region of the table?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)