[
https://issues.apache.org/jira/browse/HADOOP-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585601#action_12585601
]
Doug Cutting commented on HADOOP-3159:
--------------------------------------
+1 The new patch is acceptable. Longer-term it seems to me we need a static
login(Configuration, URI) method, and the possibility to register different
login methods for different URI schemes, e.g.,
fs.login.hdfs=UnixUserGroupInformation. The static method would then, when the
configuration has no login information invoke the login method of the class
named for that scheme, if any.
> FileSystem cache keep overwriting cached value
> ----------------------------------------------
>
> Key: HADOOP-3159
> URL: https://issues.apache.org/jira/browse/HADOOP-3159
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.16.2
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Blocker
> Fix For: 0.16.3, 0.17.0
>
> Attachments: 3159_20080402.patch, 3159_20080403.patch
>
>
> Consider the following:
> {code}
> Configuration conf1 = new Configuration();
> FileSystem fs1 = FileSystem.get(conf1); //conf1 may be modified, the cache
> key stored will use the modified values.
> Configuration conf2 = new Configuration(); //create another conf, which won't
> have the modified values.
> FileSystem fs2 = FileSystem.get(conf2); //may initialize another FileSystem
> instead of returning the cached FileSystem, since conf2 does not have the
> modified values initially.
> {code}
> Therefore, FileSystem.get(conf) may keeps creating FileSystem and replaces
> the cached one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
