Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 16 Jun 2016 16:05:05 +0000 (UTC)
From: =?utf-8?Q?Sergio_Pe=C3=B1a_=28JIRA=29?= <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12973637.1464410244000.8284.1466093105271@Atlassian.JIRA>
In-Reply-To: <JIRA.12973637.1464410244000@Atlassian.JIRA>
References: <JIRA.12973637.1464410244000@Atlassian.JIRA> <JIRA.12973637.1464410244538@arcas>
Subject: [jira] [Updated] (HIVE-13884) Disallow queries fetching more than a
 configured number of partitions in PartitionPruner
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 16 Jun 2016 16:05:07 -0000


     [ https://issues.apache.org/jira/browse/HIVE-13884?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergio Pe=C3=B1a updated HIVE-13884:
-------------------------------
    Attachment: HIVE-13884.5.patch

> Disallow queries fetching more than a configured number of partitions in =
PartitionPruner
> -------------------------------------------------------------------------=
---------------
>
>                 Key: HIVE-13884
>                 URL: https://issues.apache.org/jira/browse/HIVE-13884
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Mohit Sabharwal
>            Assignee: Sergio Pe=C3=B1a
>         Attachments: HIVE-13884.1.patch, HIVE-13884.2.patch, HIVE-13884.3=
.patch, HIVE-13884.4.patch, HIVE-13884.5.patch
>
>
> Currently the PartitionPruner requests either all partitions or partition=
s based on filter expression. In either scenarios, if the number of partiti=
ons accessed is large there can be significant memory pressure at the HMS s=
erver end.
> We already have a config {{hive.limit.query.max.table.partition}} that en=
forces limits on number of partitions that may be scanned per operator. But=
 this check happens after the PartitionPruner has already fetched all parti=
tions.
> We should add an option at PartitionPruner level to disallow queries that=
 attempt to access number of partitions beyond a configurable limit.
> Note that {{hive.mapred.mode=3Dstrict}} disallow queries without a partit=
ion filter in PartitionPruner, but this check accepts any query with a prun=
ing condition, even if partitions fetched are large. In multi-tenant enviro=
nments, admins could use more control w.r.t. number of partitions allowed b=
ased on HMS memory capacity.
> One option is to have PartitionPruner first fetch the partition names (in=
stead of partition specs) and throw an exception if number of partitions ex=
ceeds the configured value. Otherwise, fetch the partition specs.
> Looks like the existing {{listPartitionNames}} call could be used if exte=
nded to take partition filter expressions like {{getPartitionsByExpr}} call=
 does.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)