[
https://issues.apache.org/jira/browse/HADOOP-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230286#comment-13230286
]
Daryn Sharp commented on HADOOP-3257:
-------------------------------------
Per the bug that got dupped to this one, : could be handled correctly if the
RFC for URI syntax is more closely followed for scheme & authority.
* Path looks for a : and / and checks that the colon occurs before the /. It
really should be colon_index = slash_index - 1.
* There's a limited number of chars valid in a scheme. Path should stop
looking for a : if a non-valid scheme char is encountered.
That would take care of most cases. Now let's say someone _really_ does want a
relative path that looks like a URI, ex. {{foo:/bar}}. They can use
{{./foo:/bar}} to disambiguate.
I have a heap of un-submitted patches littering my home/work laptop, and one
that implements this behavior is lying around somewhere...
> Path should handle all characters
> ---------------------------------
>
> Key: HADOOP-3257
> URL: https://issues.apache.org/jira/browse/HADOOP-3257
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.17.0
> Reporter: Arun C Murthy
>
> Currently Path is limited by URI semantics in the sense that one cannot
> create files whose names include characters such as ":" etc.
> HADOOP-2066 & HADOOP-3256 are manifestations of this problem. It would be
> nice if Path handled all characters correctly...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
