hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-245) Create symbolic links in HDFS
Date Thu, 24 Sep 2009 21:58:16 GMT

    [ https://issues.apache.org/jira/browse/HDFS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759282#action_12759282
] 

Eli Collins commented on HDFS-245:
----------------------------------

Thanks Nigel, Allen, Robert for taking a look. Will update the doc
with feedback.


Good point, the NN should do the same, use the same limit for consistency.




Agree with Allen. Updated to read "fsck should not follow or report
dangling links"


Probably don't need one, seems like distcp should following links and...


would not adjust links when it's copying them.


Not sure the design doc needs to specify but how about the usual
fileName -> path?


Agree w/ Rob, links should not count towards quota (they have no
storage after all).


You're right, the above should be chmod (not ch*). And checks against
the link target should be performed regardless of what file system it
resides on. And yes ch* utilities need to be link-aware.


Agreed.  Seems like these should all go in the user guide, unless
people want them spelled out in the design doc.

Wrt lsr and rmr, I'd make them not follow links by default and add
options that do (can detect loops by remembering the paths they've
visited).

+1 to Doug's idea of exposing links solely via FileContext, so that
day zero behavior ignores links and clients get updated to be link
aware as necessary. Are people OK updating them as they move to
FileContext?

Thanks,
Eli


> 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.


Mime
View raw message