You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2008/03/12 03:30:46 UTC

[jira] Updated: (HADOOP-3003) FileSystem cache key should be updated after a FileSystem object is created

     [ https://issues.apache.org/jira/browse/HADOOP-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE updated HADOOP-3003:
-------------------------------------------

    Attachment: 3003_20080311.patch

3003_20080311.patch: should fix this problem.

> 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.