You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Mithun Radhakrishnan (JIRA)" <ji...@apache.org> on 2015/02/20 00:36:12 UTC
[jira] [Commented] (HIVE-9674) *DropPartitionEvent should handle
partition-sets.
[ https://issues.apache.org/jira/browse/HIVE-9674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328321#comment-14328321 ]
Mithun Radhakrishnan commented on HIVE-9674:
--------------------------------------------
Sorry, this patch isn't ready. {{PreDropPartitionEvent}}'s constructor doesn't take {{Iterable<Partition>}}. Also, {{HiveMetaStore}} should be sending a single {{PreDropPartitionEvent}}, instead of one per partition. Will update the patch shortly.
> *DropPartitionEvent should handle partition-sets.
> -------------------------------------------------
>
> Key: HIVE-9674
> URL: https://issues.apache.org/jira/browse/HIVE-9674
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.14.0
> Reporter: Mithun Radhakrishnan
> Assignee: Mithun Radhakrishnan
> Attachments: HIVE-9674.1.patch
>
>
> Dropping a set of N partitions from a table currently results in N DropPartitionEvents (and N PreDropPartitionEvents) being fired serially. This is wasteful, especially so for large N. It also makes it impossible to even try to run authorization-checks on all partitions in a batch.
> Taking the cue from HIVE-9609, we should compose an {{Iterable<Partition>}} in the event, and expose them via an {{Iterator}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)