[ 
https://issues.apache.org/jira/browse/HADOOP-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760486#comment-13760486
 ] 

Jason Lowe commented on HADOOP-9912:
------------------------------------

bq. I sent the calendar invite out to everyone who filled in the Doodle poll. 
[...] Let me know if you didn't receive an invite.

Thanks for organizing it, Andrew.  For some reason I have yet to see the 
invitation.  Could you please try sending it to me again?

As for the three cases:

bq. Symlink loops. If we're auto-resolving, does our directory walker infinite 
loop?

Yes, the directory walker would infinite loop.  This is similar to any simple 
directory walker on other filesystems.  The tradeoff here is all walkers work, 
unmodified, for the common cases where there isn't a loop, or they break even 
in the common case and have to update for symlink detection with no guarantee 
they will bother to do the bookkeeping for loop detection.

bq. Dangling symlinks. What happens when we hit one of these? An exception? 
Prune it from the results?

That case is covered in the proposal above.  If a symlink cannot be resolved 
then it would be returned as a symlink in the results.

bq. Symlink to another FileSystem. An HDFS symlink could link to another HDFS, 
or the local filesystem, or theoretically any implementing filesystem (e.g. S3, 
Swift). Would you really want to walk across filesystems transparently?

Yes, it would traverse to the other filesystem, just as it does on other 
filesystems (e.g.: local filesystems on Linux).  Isn't that the whole point of 
the symlink, otherwise why is it there?  I understand there will be classes of 
tools that will need to be symlink aware and not follow them in certain 
situations, but I think users would expect a symlink to be followed by most 
tools when they set it up that way.
                
> globStatus of a symlink to a directory does not report symlink as a directory
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-9912
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9912
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.3.0
>            Reporter: Jason Lowe
>            Priority: Blocker
>         Attachments: HADOOP-9912-testcase.patch, new-hdfs.txt, new-local.txt, 
> old-hdfs.txt, old-local.txt
>
>
> globStatus for a path that is a symlink to a directory used to report the 
> resulting FileStatus as a directory but recently this has changed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to