[
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.6.patch.txt
[~hagleitn] - I added a flag to TableScanOperator to mark that particular
table scan has been optimized as metadataonly. And moved the logic to the end
of analyzer because at that point the physical optimizers have finished. In
this way, both MR/Tez work, and also releases metadata only queries. I
hesitated to touch TableScanOperator but it seems no better way. What do you
think? Thanks!
> 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, HIVE-6492.6.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)
