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

Doug Cutting commented on HADOOP-4044:
--------------------------------------

> Doug should we pay the cost and do it the "right way" now?

Yes, of course.

> I prefer to use exceptions [ ... ]

But why?  You've said it's "cleaner" and "simpler".  I don't follow your 
argument.  "Simpler" could mean fewer lines of code.  I don't think it will 
actually change the lines of code much.  Changing the return types will 
*change* more lines of code, hence the change is more complex, but the 
resulting code will probably be around the same size, regardless of which 
approach is taken.  "Cleaner" is subjective, like "better", and requires 
elaboration.

My argument is that we should model normal functionality with normal 
programming: methods, parameters, return values and data structures.  Do you 
disagree with this?  Or do you think that links are not normal functionality?

You keep arguing that "exceptions can be used for recoverable conditions".  
Indeed they can.  But is a link really best modeled as a "recoverable 
condition"?  This sounds to me like a rationalization for using exceptions, not 
a reason to use exceptions over data structures.

Please provide a reasoned explanation for your disagreement.  Otherwise it is 
hard to move forward.

> Create symbolic links in HDFS
> -----------------------------
>
>                 Key: HADOOP-4044
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4044
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: symLink1.patch, symLink1.patch, 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