[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638581#action_12638581
]
Owen O'Malley commented on HADOOP-4044:
---------------------------------------
Ok, I realized after I posted that in fact the LinkResult is not abstract.
Doug> do you think this logic is unique to HDFS?
Well, currently yes, but in the long term hopefully not. In my proposal, most
of the work would happen in LinkResult.
Doug> Also, the pseudo code above will cause a stack overflow for a circular
link.
I was assuming (and included in the comments) that getNewPath would throw if it
was too deeply nested. I would probably use a thread local variable to measure
the depth of the traversal. It isn't great, but it would be encapsulated in
LinkResult.
> 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.
