[
https://issues.apache.org/jira/browse/DRILL-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092422#comment-15092422
]
Venki Korukanti commented on DRILL-4256:
----------------------------------------
Commit ({{76f41e18}}) should only affect when native reader is enabled. Not
sure why it is causing regression in this case. Is the environment same for
both the tests? Also can you run jstack while the query is running and check
the callstack?
> Performance regression in hive planning
> ---------------------------------------
>
> Key: DRILL-4256
> URL: https://issues.apache.org/jira/browse/DRILL-4256
> Project: Apache Drill
> Issue Type: Bug
> Components: Functions - Hive, Query Planning & Optimization
> Affects Versions: 1.5.0
> Reporter: Rahul Challapalli
>
> Commit # : 76f41e18207e3e3e987fef56ee7f1695dd6ddd7a
> The fix for reading hive tables backed by hbase caused a performance
> regression. The data set used in the below test has ~3700 partitions and the
> filter in the query would ensure only 1 partition get selected.
> {code}
> Commit : 76f41e18207e3e3e987fef56ee7f1695dd6ddd7a
> Query : explain plan for select count(*) from lineitem_partitioned where
> `year`=2015 and `month`=1 and `day` =1;
> Time : ~25 seconds
> {code}
> {code}
> Commit : 1ea3d6c3f144614caf460648c1c27c6d0f5b06b8
> Query : explain plan for select count(*) from lineitem_partitioned where
> `year`=2015 and `month`=1 and `day` =1;
> Time : ~6.5 seconds
> {code}
> Since the data is large, I couldn't attach it here. Reach out to me if you
> need additional information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
