[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637348#action_12637348
]
Konstantin Shvachko commented on HADOOP-4044:
---------------------------------------------
Owen is proposing a reasonable rename of the FSLink*** classes. But the
implementations of these classes remain the same.
Going further this way we could make the API look like this:
{code}
RenameReply rename(RenameRequest arg) throws IOException;
{code}
This is universal, but not a transparent api anymore.
The next step to completely generalize (and exaggerate) this would be to
declare one single protocol method.
{code}
Reply execute(enum opCode, Request arg) throws IOException;
{code}
Then the api will have to be defined by a pair of Request, Reply classes.
> 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.
