[
https://issues.apache.org/jira/browse/HIVE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531809#comment-14531809
]
Sushanth Sowmyan commented on HIVE-9736:
----------------------------------------
Also, since this is a performance patch rather than an outtage or regression,
and since it is not trivial either, I'm marking it as tentative for inclusion
to 1.2.0, i.e. if it gets done in time, we will include it, but if not, we mark
it for 1.2.1
> 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
> Fix For: 1.2.0
>
> Attachments: HIVE-9736.1.patch, HIVE-9736.2.patch, HIVE-9736.3.patch,
> HIVE-9736.4.patch, HIVE-9736.5.patch, HIVE-9736.6.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)
