[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639653#action_12639653
]
Sanjay Radia commented on HADOOP-4044:
--------------------------------------
Owen> 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.
Doug> I see. Yuck.
I second the Yuck.
Doug> Perhaps we're prematurely optimizing here. Perhaps the extra RPCs to
resolve paths won't hurt things that much.
The above was in reference to Dhruba's approach of using the FSLinkResolver
abstract class verses Owen's more inline approach.
While Dhruba's FSLinkResolver is a little more complex, it is not complex
enough to warrant doing the additional RPC.
We might be able to further simplify it by using a LinkableFileSystem base
class as Doug suggested.
I really don't like the extra rpc for any method that has a pathname as a
parameter regardless of whether or not a link is in the path.
> 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: HADOOP-4044-strawman.patch, 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.
