[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-4044:
---------------------------------
Attachment: HADOOP-4044-strawman.patch
> I guess we need an openImpl(...) method. Otherwise, it would be an infinite
> loop.
No, they have different signatures. I've attached a patch for FileSystem that
implements this. For FileSystem's that do not support links this is completely
back-compatible. HDFS could implement this by adding an RPC per file before it
is opened. If that proves too slow, it could perhaps optimize things by
returning and caching the block list with the link information, so that a
second RPC could be avoided.
The patch is not complete, but it works. I've only implemented open. It's
meant to be an illustration of a style that we might use.
> 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.
