[
https://issues.apache.org/jira/browse/HIVE-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915648#comment-13915648
]
Gunther Hagleitner commented on HIVE-6492:
------------------------------------------
[~selinazh]: There's a similar safety variable already present in hive:
HiveConf.ConfVars.HIVEMAPREDMODE / hive.mapred.mode
When turned on it enforces that every query has a condition that prunes
partitions from the table it's running against. It's not the same but very
similar and might satisfy your requirements. The assumption is that if a user
has added a pruning condition they have though about properly limiting the
amount of data to be scanned. Does that work for you?
> 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
>
> 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.1.5#6160)
