You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Daniel Barclay (JIRA)" <ji...@apache.org> on 2016/10/04 13:49:20 UTC

[jira] [Updated] (HADOOP-13679) org.apache.hadoop.fs.Path doesn't specify mentioned differences from URIs

     [ https://issues.apache.org/jira/browse/HADOOP-13679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Barclay updated HADOOP-13679:
------------------------------------
    Description: 
The documentation comment on {{org.apache.hadoop.fs.Path.Path(String)}} says:
bq. Path strings are URIs, but with unescaped elements and some additional normalization.

However, neither that comment nor {{org.apache.hadoop.fs.Path}}'s documentation comment says anything further about exactly what the differences between URI and {{org.apache.hadoop.fs.Path}} strings are.


(Knowing what {{Path}} strings are supposed to be is important for determining whether the code is buggy or not.

In particular, it seems that {{Path(String)}} and friends _might_ parse the scheme portion incorrectly (taking anything before a (first) colon rather than following the RFC 3986 syntax of:
bq. {{scheme      = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )}}
).)


So what exactly are the actual differences between {{Path}} string syntax and URI syntax?

(I might be able to submit a PR with documentation changes, but I need the raw information first.)

  was:
The documentation comment on {{org.apache.hadoop.fs.Path.Path(String)}} says:
bq. Path strings are URIs, but with unescaped elements and some additional normalization.

However, neither that comment nor {{org.apache.hadoop.fs.Path}}'s documentation comment says anything further about exactly what the differences between URI and {{org.apache.hadoop.fs.Path}} strings are.


(Knowing what {{Path}} strings are supposed to be is important for determining whether the code is buggy or not.

In particular, {{Path(String)}} and friends seem to parse the scheme portion incorrectly (taking anything before a (first) colon rather than following the RFC 3986 syntax of:
bq. {{scheme      = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )}}
).)


So what exactly are the actual differences between {{Path}} string syntax and URI syntax?

(I might be able to submit a PR with documentation changes, but I need the raw information first.)


> org.apache.hadoop.fs.Path doesn't specify mentioned differences from URIs
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-13679
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13679
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Daniel Barclay
>
> The documentation comment on {{org.apache.hadoop.fs.Path.Path(String)}} says:
> bq. Path strings are URIs, but with unescaped elements and some additional normalization.
> However, neither that comment nor {{org.apache.hadoop.fs.Path}}'s documentation comment says anything further about exactly what the differences between URI and {{org.apache.hadoop.fs.Path}} strings are.
> (Knowing what {{Path}} strings are supposed to be is important for determining whether the code is buggy or not.
> In particular, it seems that {{Path(String)}} and friends _might_ parse the scheme portion incorrectly (taking anything before a (first) colon rather than following the RFC 3986 syntax of:
> bq. {{scheme      = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )}}
> ).)
> So what exactly are the actual differences between {{Path}} string syntax and URI syntax?
> (I might be able to submit a PR with documentation changes, but I need the raw information first.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org