[
https://issues.apache.org/jira/browse/HADOOP-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031642#comment-13031642
]
Hudson commented on HADOOP-7268:
--------------------------------
Integrated in Hadoop-Common-trunk #685 (See
[https://builds.apache.org/hudson/job/Hadoop-Common-trunk/685/])
HADOOP-7268. FileContext.getLocalFSFileContext() behavior needs to be fixed
w.r.t tokens. Contributed by jitendra.
> FileContext.getLocalFSFileContext() behavior needs to be fixed w.r.t tokens
> ---------------------------------------------------------------------------
>
> Key: HADOOP-7268
> URL: https://issues.apache.org/jira/browse/HADOOP-7268
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs, security
> Affects Versions: 0.23.0
> Reporter: Devaraj Das
> Assignee: Jitendra Nath Pandey
> Fix For: 0.23.0
>
> Attachments: HADOOP-7268.1.patch
>
>
> FileContext.getLocalFSFileContext() instantiates a FileContext object upon
> the first call to it, and for all subsequent calls returns back that instance
> (a static localFsSingleton object). With security turned on, this causes some
> hard-to-debug situations when that fileContext is used for doing HDFS
> operations. This is because the UserGroupInformation is stored when a
> FileContext is instantiated. If the process in question wishes to use
> different UserGroupInformation objects for different file system operations
> (where the corresponding FileContext objects are obtained via calls to
> FileContext.getLocalFSFileContext()), it doesn't work.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
