hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3003) FileSystem cache key should be updated after a FileSystem object is created
Date Wed, 12 Mar 2008 21:22:46 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578020#action_12578020
] 

Doug Cutting commented on HADOOP-3003:
--------------------------------------

> Do you want me to remove it or keep it for future use?

Please remove it.  We should not keep dead code around for future use, since plans often change
and then we end up with just dead code.




> FileSystem cache key should be updated after a FileSystem object is created
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-3003
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3003
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.17.0
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>             Fix For: 0.17.0
>
>         Attachments: 3003_20080311.patch
>
>
> In FileSystem.get(uri, conf), it first creates a cache key from the uri and the conf
and then lookups the corresponding FileSystem object in the cache.  If the object is not found,
it initializes a FileSystem object and put it to the cache with the key.  However, during
FileSystem creation, the conf might be modified.  In such case, the key should be updated
before putting it to the cache.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message