[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630444#action_12630444
]
Allen Wittenauer commented on HADOOP-4044:
------------------------------------------
-1 to both, because I think we're rushing this without a significant amount of
thought as to what a multi-filesystem directory structure should look like.
In my mind, cross-filesystem "symlinks" really don't seem like "real" symlinks
to me, but a sort of hacked version of autofs support. How do you determine if
a file is "real" or not? How do I "undo" a symlink? What does this look like
from an audit log perspective? Is this really just a "short cut" to providing
the equivalent of mount?
If we ignore what I said above :) , I'm trying to think of a use case where I
wouldn't want to symlink an entire dir. A single file? Really?
I think it is much more interesting to provide a symlink to a directory. I can
have "data/v1.423" and then have a symlink called LATEST that points to the
latest version of a given versioned data set.
> 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
>
>
> 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.
