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

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

Hey Konstantin,

Thanks for posting the overview. Looks good, though it's not just Doug who 
would prefer not using exceptions for normal control flow. But aside from the 
issue of the use of exceptions is there consensus, eg on the user-visible 
behavior of the latest patches? If so, sorry, wasn't clear from the comments.

> There were no explanations on the fact of reassignment of this jira. Eli, are 
> you committing to support this 
> patch or do you see your mission to provide documentation and testing?

Apologies for the missing context. Dhruba hasn't had the cycles to close the 
jira and I offered to help out. It wasn't clear if people were OK with the 
latest patches so I'll work on  working on finishing them up so they're 
acceptable to people. Yes, I'm committed to supporting the feature. 

> My personal preference is approach VI. 

Do you mean approach V? 

It seems the use of symbolic links will be a common case (eg you can imagine 
them being used ala google namespaces) and therefore it would be nice to avoid 
multiple round trips to the NN.

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: Eli Collins
>         Attachments: 4044_20081030spi.java, 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, 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.

Reply via email to