hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4655) FileSystem.CACHE should be ref-counted
Date Mon, 16 Mar 2009 21:37:50 GMT

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

dhruba borthakur commented on HADOOP-4655:

> Except we don't add new features to branches, but only to trunk, right?

Sounds perfect to me. It is just that 0.20 is an "unreleased" branch.

> Also, what's the use case for newInstanceLocal()? 

An application that uses newInstance() method assumes that a new filesystem object is created
(irrespective of the path that is being passed in). It does not matter whether it is a local
path or a hdfs path. The application logic does not have to change depending on the FileSystem
that it is trying to access. So, I would like to keep the newInstanceLocal() method. 

> FileSystem.CACHE should be ref-counted
> --------------------------------------
>                 Key: HADOOP-4655
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4655
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs, fs
>    Affects Versions: 0.18.1, 0.18.2, 0.19.0, 0.19.1, 0.20.0
>            Reporter: Hong Tang
>            Assignee: dhruba borthakur
>             Fix For: 0.20.0
>         Attachments: FileSystemUnique.patch, FileSystemUnique.txt, FileSystemUnique2.txt
> FileSystem.CACHE is not ref-counted, and could lead to resource leakage.

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

View raw message