[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637319#action_12637319
]
Konstantin Shvachko commented on HADOOP-4044:
---------------------------------------------
> public class FsReturnType<T>
Interesting idea. You will rather have something like
{code}
public class FSReturnType<T extends Writable> implements Writable {
public T getValue();
Path getLink() throws IOException;
}
{code}
And implement serialization methods, and think how to define WritableFactory
for the parametrized class.
And then the protocol methods will look like this
{code}
public FSReturnType<BooleanWritable> setReplication(String src,...);
{code}
This is better than creating a new class for every new return type, but seems
rather complex compared to one new protocol method plus the
UnresolvedPathException that I was proposing.
> 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.
