[
https://issues.apache.org/jira/browse/HIVE-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923257#comment-13923257
]
Gunther Hagleitner commented on HIVE-6492:
------------------------------------------
[~selinazh] limit_partition_3.q:
The query (select count(*) from part) will succeed if you turn ON
compute.query.using.stats and will fail if you turn it off. That's because in
the first case it doesn't do a table scan, while in the second it does. (the
limit_partition_3.q.out is hard to read, but you can see it there).
The (select hr from srcpart) ... yeah you're right. I missed that. Let me take
another look.
> limit partition number involved in a table scan
> -----------------------------------------------
>
> Key: HIVE-6492
> URL: https://issues.apache.org/jira/browse/HIVE-6492
> Project: Hive
> Issue Type: New Feature
> Components: Query Processor
> Affects Versions: 0.12.0
> Reporter: Selina Zhang
> Fix For: 0.13.0
>
> Attachments: HIVE-6492.1.patch.txt, HIVE-6492.2.patch.txt,
> HIVE-6492.3.patch.txt, HIVE-6492.4.patch.txt, HIVE-6492.4.patch_suggestion,
> HIVE-6492.5.patch.txt
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> To protect the cluster, a new configure variable
> "hive.limit.query.max.table.partition" is added to hive configuration to
> limit the table partitions involved in a table scan.
> The default value will be set to -1 which means there is no limit by default.
> This variable will not affect "metadata only" query.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
