Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 9 Apr 2015 06:15:12 +0000 (UTC)
From: "Mithun Radhakrishnan (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12776346.1424400982000.36685.1428560112328@Atlassian.JIRA>
In-Reply-To: <JIRA.12776346.1424400982000@Atlassian.JIRA>
References: <JIRA.12776346.1424400982000@Atlassian.JIRA>
 <JIRA.12776346.1424400982873@arcas>
Subject: [jira] [Updated] (HIVE-9736) StorageBasedAuthProvider should batch
 namenode-calls where possible.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mithun Radhakrishnan updated HIVE-9736:
---------------------------------------
    Attachment: HIVE-9736.2.patch

The rebased patch, as promised. 

> StorageBasedAuthProvider should batch namenode-calls where possible.
> --------------------------------------------------------------------
>
>                 Key: HIVE-9736
>                 URL: https://issues.apache.org/jira/browse/HIVE-9736
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore, Security
>            Reporter: Mithun Radhakrishnan
>            Assignee: Mithun Radhakrishnan
>         Attachments: HIVE-9736.1.patch, HIVE-9736.2.patch
>
>
> Consider a table partitioned by 2 keys (dt, region). Say a dt partition could have 10000 associated regions. Consider that the user does:
> {code:sql}
> ALTER TABLE my_table DROP PARTITION (dt='20150101');
> {code}
> As things stand now, {{StorageBasedAuthProvider}} will make individual {{DistributedFileSystem.listStatus()}} calls for each partition-directory, and authorize each one separately. It'd be faster to batch the calls, and examine multiple FileStatus objects at once.


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