hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <>
Subject [jira] [Commented] (HIVE-6492) limit partition number involved in a table scan
Date Tue, 25 Mar 2014 21:59:17 GMT


Ashutosh Chauhan commented on HIVE-6492:

I left following comment:
bq. I thought you want this limit to be applied on cumulative partitions count or limit is
meant for per TSOperator? 

I see you don't updated that part of code. Was it intentional? Currently, limit would be considered
per TSOperator (table), not across all tables referred in query. Either way is fine with me,
just want to confirm you intend limit per table, not across all tables in query.
Other than looks good.

> limit partition number involved in a table scan
> -----------------------------------------------
>                 Key: HIVE-6492
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: Query Processor
>    Affects Versions: 0.12.0
>            Reporter: Selina Zhang
>            Assignee: Ashutosh Chauhan
>             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

View raw message