[
https://issues.apache.org/jira/browse/DRILL-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979671#comment-14979671
]
ASF GitHub Bot commented on DRILL-3623:
---------------------------------------
Github user sudheeshkatkam commented on the pull request:
https://github.com/apache/drill/pull/193#issuecomment-152053724
I think I see the source of confusion (sorry); this patch does not address
that query in the JIRA, which is why Jinfeng asked me to change the title in
one of his comments. Regarding that query, DRILL-3921 helps avoids most of the
execution time, but we still incur the planning time. And my initial approach
address this issue but as mentioned above, this is blocked by DRILL-2288 and
other things.
The new approach actually addresses any query that has a limit 0 above a
blocking operator that consumes all records. And avoiding parallelization made
the query much worse. (Actually, was fast-schema supposed to still kick in? Did
not seem like it from my experiments.)
I tested against a query like `SELECT * FROM (SELECT COUNT(DISTINCT a),
COUNT(DISTINCT b), COUNT(DISTINCT c) FROM very_large_table) T LIMIT 0` and this
completed two orders of magnitude faster.
> Hive query hangs with limit 0 clause
> ------------------------------------
>
> Key: DRILL-3623
> URL: https://issues.apache.org/jira/browse/DRILL-3623
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Hive
> Affects Versions: 1.1.0
> Environment: MapR cluster
> Reporter: Andries Engelbrecht
> Assignee: Jinfeng Ni
> Fix For: Future
>
>
> Running a select * from hive.table limit 0 does not return (hangs).
> Select * from hive.table limit 1 works fine
> Hive table is about 6GB with 330 files with parquet using snappy compression.
> Data types are int, bigint, string and double.
> Querying directory with parquet files through the DFS plugin works fine
> select * from dfs.root.`/user/hive/warehouse/database/table` limit 0;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
