[
https://issues.apache.org/jira/browse/HADOOP-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268623#comment-13268623
]
John George commented on HADOOP-6356:
-------------------------------------
An issue that was raised as part of HADOOP-8319 is that in cases where there
are symlinks that point to a different FS than the defaultFS, we will lose any
state that is maintained by the client. So, for example, the setWriteChecksum
or setVerifyChecksum, which are flags that are maintained by the client will be
lost since for each instance of the call, we create a new object.
The reason I raise that here is because it seemed very similar to what is
being discussed here. My proposal is that we keep a table of each instance of
the filesystem that is not the defaultFS so that we can keep going back to the
same instance of the FS within a filecontext. This would also help in a case if
we were to ever decide to add anything that requires state to be maintained on
the client side.
> Add a Cache for AbstractFileSystem in the new FileContext/AbstractFileSystem
> framework.
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-6356
> URL: https://issues.apache.org/jira/browse/HADOOP-6356
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 0.22.0
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
>
> The new filesystem framework, FileContext and AbstractFileSystem does not
> implement a cache for AbstractFileSystem.
> This Jira proposes to add a cache to the new framework just like with the old
> FileSystem.
--
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
