[
https://issues.apache.org/jira/browse/HDFS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759334#action_12759334
]
dhruba borthakur commented on HDFS-245:
---------------------------------------
The FileContext API is not yet clearly baked as far as I can tell. I would like
the FileSystem API to do the right thing about symlinks untill the time we
deprecate it and make aps avoid FileSystem completely. I think we should avoid
making apps use FileContext if they want to use symlinks. If one is worried
about how existing apps behave in the presence of symlinks, then that
adminstrator can set dfs.support.symlinks to false. This is a server side
config that prevents the creation of symlinks.
distcp and har should avoid following symlinks by default. I will create a JIRA
that will make these utilities support an option to allow following symlinks.
@Robert: I udnerstand your concern about day-zero behaviour. will it satisfy
you if dfs.support.symlinks is set to false by default?
@Allen: fsck just reports the number of symlinks it found. It does not follow
them. Also, this patch does not implement "chown -h (POSIX) and chown -H, chown
-L, and chown -P (SVID?)". Can I implement them in a subsequent JIRA?
> 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.
