[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637286#action_12637286
]
Tsz Wo (Nicholas), SZE commented on HADOOP-4044:
------------------------------------------------
I think it is wrong to combine FSLink and the original return type like
boolean, BlockLocations, etc. to create new classes. The problem here is that
we need to return two items in a single method call. The usually approach is to
return a container, say FsReturnType<T>. I suggest the following API:
{code}
//T is the original type
public class FsReturnType<T> {
public T getValue() {
...
}
Path getLink() throws IOException {
...
}
}
{code}
BTW, should our naming convention be FsXxx or FSXxx?
> 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.
