[ https://issues.apache.org/jira/browse/HIVE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518834#comment-14518834 ]
Mithun Radhakrishnan commented on HIVE-9736: -------------------------------------------- Hello, Chris. bq. ... we can combine the multiple actions by using FsAction#or, and then call accessMethod.invoke just once... Yikes! I might've missed incorporating that suggestion by accident. Thank you for following up. I'll update the patch shortly. > 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, HIVE-9736.3.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)