hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4044) Create symbolic links in HDFS
Date Thu, 09 Oct 2008 02:01:44 GMT

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

Owen O'Malley commented on HADOOP-4044:

   I don't see your point. Clearly this is not black and white at all or it wouldn't have
caused so much disagreement among the developers.  I still think the core disagreement is
whether hitting a link is enough of an exception to be reasonably implemented as a Java exception.
Most of the rest of it I consider supporting arguments. *smile*

In particular, we aren't changing the FileSystem API at all. No client code should be able
to detect the difference between the versions before and after. What is changing is the RPC
layer and I agree that we effectively have a tagged union between the link result and the
actual result. I still don't think either is very nice looking, which is why I was falling
back to supporting arguments.

I think defining result types will give us significant advantages going forward.
  1. It is easy to add additional information in a forward/backward compatible manner.
  2. It is declared and strongly type checked.
  3. It doesn't throw exceptions. *grin*

> Create symbolic links in HDFS
> -----------------------------
>                 Key: HADOOP-4044
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4044
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: symLink1.patch, symLink1.patch, symLink4.patch, symLink5.patch,
symLink6.patch, symLink8.patch, symLink9.patch
> HDFS should support symbolic links. A symbolic link is a special type of file that contains
a reference to another file or directory in the form of an absolute or relative path and that
affects pathname resolution. Programs which read or write to files named by a symbolic link
will behave as if operating directly on the target file. However, archiving utilities can
handle symbolic links specially and manipulate them directly.

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

View raw message