[ https://issues.apache.org/jira/browse/HADOOP-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792767#action_12792767 ]
Sanjay Radia commented on HADOOP-6427: -------------------------------------- Doug> Symbolic links should be resolved relative to their source location. So hdfs://x/foo - > /bar should be interpreted as a link to hdfs://x/bar. Is this because it is being interpreted relative to the volume root (ie hdfs://x) or because it us being interpreted relative to the client context, ie the client's root (/). The client's root might be file:///. I agree with your statement "Symbolic links should be resolved relative to their source location" if by "source" you mean the place where the symlink occurs. In the HDFS-245 jira I called links like /bar to be volume-root-relative sym links. As I pointed out in my previous comment that there are use cases for both. > Add Path isQualified > -------------------- > > Key: HADOOP-6427 > URL: https://issues.apache.org/jira/browse/HADOOP-6427 > Project: Hadoop Common > Issue Type: Improvement > Reporter: Eli Collins > Assignee: Eli Collins > Attachments: hadoop-6427-1.patch > > > The Path class has a method to make a path qualified but not to query if the > path is qualified. This is needed for HADOOP-64221. In addition this patch > adds tests to TestPath that cover the file scheme. Note that "fully > qualified" applies to domain names not URIs so this function and it tests > also serve to define what we mean by a fully qualified path. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.