[
https://issues.apache.org/jira/browse/HADOOP-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291095#comment-13291095
]
Daryn Sharp commented on HADOOP-8490:
-------------------------------------
Good points, but I think the issue of sanely managing dynamic vs static values
is a separate issue. On that tangent, {{FileSystem}} probably isn't a good
place to make that decision since the actual underlying clients of the
filesystems are the ones that need to make that determination. It's a much
harder problem than this one.
In this jira, I'm only proposing that a user can take specific action to ensure
a unique yet cached fs instance can be created and later closed.
> Add Configuration to FileSystem cache key
> -----------------------------------------
>
> Key: HADOOP-8490
> URL: https://issues.apache.org/jira/browse/HADOOP-8490
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.23.0, 0.24.0, 2.0.0-alpha
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
>
> The {{FileSystem#get(URI, Configuration}} does not take the given
> {{Configuration}} into consideration before returning an existing fs instance
> from the cache with a possibly different conf.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
