[
https://issues.apache.org/jira/browse/HDFS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759368#action_12759368
]
eric baldeschwieler commented on HDFS-245:
------------------------------------------
So who is going to takeout the trash if we half implement this now? Half
implemented features have a way of really turning around and biting us. I'd
hate to see us move the system to a place where the API was not well defined or
was inconsistent about the handling of something this basic.
There are a lot of spec questions still open! I'd suggest this feature still
has a lot of work to go and should either go into a branch or live as a
expanding patch until folks feel it is complete. It is certainly not ready to
be back ported to 21.
I'm fine with only doing it in file context... if we wait to checkin symlinks
until FileSystem is fully deprecated.
I'd suggest that we should follow the posix conventions here as closely as
possible. We should understand why we are diverging anywhere we do diverge.
This discussion has convinced me we need a pretty complete spec & a lot of
testing before we can add this. it will be easier to build a spec if we start
with posix's and then look for problems...
> Create symbolic links in HDFS
> -----------------------------
>
> Key: HDFS-245
> URL: https://issues.apache.org/jira/browse/HDFS-245
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: 4044_20081030spi.java, designdocv1.txt,
> HADOOP-4044-strawman.patch, symlink-0.20.0.patch, symLink1.patch,
> symLink1.patch, symLink11.patch, symLink12.patch, symLink13.patch,
> symLink14.patch, symLink15.txt, symLink15.txt, symlink16-common.patch,
> symlink16-hdfs.patch, symlink16-mr.patch, symlink17-common.txt,
> symlink17-hdfs.txt, 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.
