[ https://issues.apache.org/jira/browse/HIVE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995221#comment-16995221 ]
Mithun Radhakrishnan commented on HIVE-9736: -------------------------------------------- [~zshao], sorry I missed your comment. You're right about this not being faster today, since the DFSClient currently just loops on the client-side. The intention was for the file-list to be pushed down to the name-node, so as to avoid the loop. We intended to request for the {{DFSClient}} to implement this. :/ > 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 > Affects Versions: 1.2.1 > Reporter: Mithun Radhakrishnan > Assignee: Mithun Radhakrishnan > Priority: Major > Labels: TODOC1.2 > 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, HIVE-9736.7.patch, > HIVE-9736.8.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 (v8.3.4#803005)