[
https://issues.apache.org/jira/browse/HADOOP-10019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655011#comment-15655011
]
David Ongaro commented on HADOOP-10019:
---------------------------------------
I'm tired waiting for this feature. I guess by now we can safely say it's
complexity was underestimated all along. But in fact I think it was also way
too ambitious. Most use cases should be already covered with a "hardlink" like
feature. With that I mean just an alias within the namenode to the same files.
That should be implementable (I hope) in a transparent way without having to
change every HDFS tool/library.
One of the main features of symlinks is that one can link to other filesystem,
but for me it seems this would not even be an option for HDFS, because we
expect certain performance characteristics of HDFS. So what would we even get
that hardlinks can't do? Hardlinks would also avoid having to think about all
these complex problems like link cycles.
So please retire this and lets get hardlinks rolling. We still could get back
to this if the need arises afterwards.
> make symlinks production-ready
> ------------------------------
>
> Key: HADOOP-10019
> URL: https://issues.apache.org/jira/browse/HADOOP-10019
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 2.3.0
> Reporter: Colin P. McCabe
> Assignee: Ajith S
>
> This is an umbrella JIRA for all the things we have to do to make symlinks
> production-ready for Hadoop 2.3.
> Note that some of these subtasks are scheduled for 2.1.2 / 2.2, but the
> overall effort is for 2.3.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
