[
https://issues.apache.org/jira/browse/HADOOP-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585223#action_12585223
]
Raghu Angadi commented on HADOOP-3159:
--------------------------------------
Digressing a little bit, the fundamental confusion seems to be that the key
used by the cache needs scheme, authority, and username, but it only requires
scheme and authority for look up.. so tries derive username some how. In long
term, hopefully the interface itself gets fixed.
> 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
>
>
> 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.
