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 16:20:46 GMT

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

Doug Cutting commented on HADOOP-3003:

In particular, I think you mean that the user information in the configuration could have
been modified by a login process, and that we want the updated user information.  Is that

Also, I don't see why FsRef needs a Key, why cache values cannot just be FileSystem instances.
 The only place where the FsRef's key is used is in closeAll(), where map.entrySet() could
be instead used to iterate through all key/value pairs, no?

> 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
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>             Fix For: 0.16.2
>         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.

View raw message