[jira] [Commented] (HIVE-9736) StorageBasedAuthProvider should batch namenode-calls where possible.

["Mithun Radhakrishnan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334157#comment-14334157 ] 

Mithun Radhakrishnan commented on HIVE-9736:
--------------------------------------------

Tagging [~thejas], since this marches all over the security-work (and SBAP).

Sorry the patch looks a little big... The actual changes aren't, really.

> 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
>
>
> 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)