[
https://issues.apache.org/jira/browse/HIVE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531704#comment-14531704
]
Sergio Peña commented on HIVE-9736:
-----------------------------------
Hi [~mithun]
This patch is causing the above tests to fail due to the change on
{{Hadoop23Shims.checkFileAccess(FileSystem fs, Iterator<FileStatus> statuses,
EnumSet<FsAction> actions)}}.
The line that fails is {{accessMethod.invoke(fs, statuses.next(),
combine(actions));}}
I an running hadoop 2.6.0, and the FileSystem.access() object accepts a Path
and FsAction. When I run the code that checks patch permissions, I get this
error:
{noformat}
hive> explain select * from a join b on a.id = b.id;
FAILED: SemanticException Unable to determine if
hdfs://localhost:9000/user/hive/warehouse/a is read only:
java.lang.IllegalArgumentException: argument type mismatch
{noformat}
Is there a follow-up jira for this error?
> 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)
