[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637555#action_12637555
]
Sanjay Radia commented on HADOOP-4044:
--------------------------------------
Sanjay Saya:
>> Are you saying that getSymlink() can return file:///etc/dir/file.txt?
>Yes.
>Can the name node always know how to compose the two parts. I recall something
>bizzare about the composing archive filesystem paths.
>If there is well defined way of composing the two parts then I am fine with
>the alternative proposed above.
>If not, the two parts may have to be passed to the file system.
I checked - the above scheme will work with archives. It uses the standard
separator.
+1 on the getSymlink returning the composed pathname.
> 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.
