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

Sanjay Radia commented on HADOOP-9984:
--------------------------------------

[~asuresh] thanks for your comment on Hive.
* if you configure hiveserver2 with sql-standard-auth then the file system 
permissions do not apply and symlinks should not be an issue. The data should 
be owned by hiverserver and users should not have hdfs access to those 
directories and files.,
* if you configure file-system-auth then the issue you describe will occur 
*when impersonation is tuned off*. Recall we had to fix Hive to work with 
encryption; likewise Hive will need to understand symlinks. To deal with 
atomicity issues (race between checking and setting symlink) we may have to add 
an api to HDFS to resolve to inode# and then resolve from inode#. (HDFS does 
have inode number that were added for NFS.). However, isn't file-system-auth 
usually used with impersonation where symlinks are not an issue?
* With impersonation turned on, the job will run as the user and symlinks will 
work. Correct?

> FileSystem#globStatus and FileSystem#listStatus should resolve symlinks by 
> default
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-9984
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9984
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs
>    Affects Versions: 2.1.0-beta
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Critical
>              Labels: BB2015-05-TBR
>         Attachments: HADOOP-9984.001.patch, HADOOP-9984.003.patch, 
> HADOOP-9984.005.patch, HADOOP-9984.007.patch, HADOOP-9984.009.patch, 
> HADOOP-9984.010.patch, HADOOP-9984.011.patch, HADOOP-9984.012.patch, 
> HADOOP-9984.013.patch, HADOOP-9984.014.patch, HADOOP-9984.015.patch
>
>
> During the process of adding symlink support to FileSystem, we realized that 
> many existing HDFS clients would be broken by listStatus and globStatus 
> returning symlinks.  One example is applications that assume that 
> !FileStatus#isFile implies that the inode is a directory.  As we discussed in 
> HADOOP-9972 and HADOOP-9912, we should default these APIs to returning 
> resolved paths.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to