[
https://issues.apache.org/jira/browse/DRILL-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206798#comment-15206798
]
ASF GitHub Bot commented on DRILL-3623:
---------------------------------------
Github user StevenMPhillips commented on the pull request:
https://github.com/apache/drill/pull/405#issuecomment-199910572
Sudheesh, could you respond to the comments made by Jin Feng? If you have
already discussed it with him in person, could you post a summary here.
I am in favor of merging this PR, but just the last commit. I think the
second commit should be separate, and should be done as an inserted operator
(similar to IteratorValidator), rather than modifying the constructor for
Screen.
> Limit 0 should avoid execution when querying a known schema
> -----------------------------------------------------------
>
> Key: DRILL-3623
> URL: https://issues.apache.org/jira/browse/DRILL-3623
> Project: Apache Drill
> Issue Type: Sub-task
> Components: Storage - Hive
> Affects Versions: 1.1.0
> Environment: MapR cluster
> Reporter: Andries Engelbrecht
> Assignee: Sudheesh Katkam
> Labels: doc-impacting
> 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)
