[
https://issues.apache.org/jira/browse/HADOOP-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530261
]
Chris Douglas commented on HADOOP-1891:
---------------------------------------
I see now what you meant, and I retract my point: the existing behavior matches
expectations, except as in the original example.
Coupled with HADOOP-1909, I like the idea of leaving Paths relative until
dereferenced within a FileSystem. Would it make sense to go further and
*require* all Paths to be dereferenced this way? There's a lot of string
manipulation and special-casing in Path, particularly for Windows filesystems.
Pushing that out to the FS seems like a reasonable abstraction. Introducing a
new type would also let users employ POSIX semantics for Paths, but URI
semantics for Hadoop Paths (as in HADOOP-1858). The new type could even be a
subtype of Path, where Path assumes the default FileSystem where it's used in a
URI context (just as it does now). It would be a pervasive/risky change,
though...
> "." is converted to an empty path
> ---------------------------------
>
> Key: HADOOP-1891
> URL: https://issues.apache.org/jira/browse/HADOOP-1891
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.14.1
> Environment: Linux
> Reporter: Olga Natkovich
> Assignee: Chris Douglas
>
> Path p = new Path(".");
> System.out.println("path=(" + p.toString() +")");
> path =()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
