[
https://issues.apache.org/jira/browse/DRILL-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979395#comment-14979395
]
ASF GitHub Bot commented on DRILL-3623:
---------------------------------------
Github user jacques-n commented on the pull request:
https://github.com/apache/drill/pull/193#issuecomment-152018974
Got it. Thanks for the explanation. So this is a hack until we can solve
those issues.
I think we have to do this work, however. a 1-2 second response to a limit
0 query is too much. We should open up jiras for all of these inconsistency
issues and then get Calcite and Drill in alignment.
What do you think we're talking about: aggregation outputs, implicit
casting. What else?
> 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)
