[
https://issues.apache.org/jira/browse/HIVE-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selina Zhang updated HIVE-6492:
-------------------------------
Attachment: HIVE-6492.4.patch.txt
Gunther, thanks for your comments!
Removed the logic for simple fetch query. Let the query pass if it is a fetch
operator (no mapreduce job launched).
However, I still need to put the logic right after the physical optimizers
because only till then I have the information that if the query is a metadata
only query.
> 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
>
> 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)
