[
https://issues.apache.org/jira/browse/HDFS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148925#comment-13148925
]
Tsz Wo (Nicholas), SZE commented on HDFS-2316:
----------------------------------------------
Alejandro,
We are getting very close. All except #2 are documentation discussion. Let's
continue documentation related discussion in HDFS-2552. I will response to
your other points there.
For #2, the reason of having "urlString" is to allow changing encoding/token
format later on, e.g.
{noformat}
{"Token": { "newEncoding" : <TOKEN> } }
{noformat}
For path, it seems using a string is just fine. But if you disagree, I have no
problem to change the JSON response for GETHOMEDIRECTORY to
{noformat}
{"string": <PATH_STRING>}
{noformat}
Which one do you prefer, {"string": <PATH>} or {"Path": <PATH>}?
BTW, thank you so much for all the comments. They are all very helpful!
> webhdfs: a complete FileSystem implementation for accessing HDFS over HTTP
> --------------------------------------------------------------------------
>
> Key: HDFS-2316
> URL: https://issues.apache.org/jira/browse/HDFS-2316
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Attachments: WebHdfsAPI20111020.pdf, WebHdfsAPI20111103.pdf,
> WebHdfsAPI20111111.pdf, test-webhdfs, test-webhdfs-0.20s
>
>
> We current have hftp for accessing HDFS over HTTP. However, hftp is a
> read-only FileSystem and does not provide "write" accesses.
> In HDFS-2284, we propose to have webhdfs for providing a complete FileSystem
> implementation for accessing HDFS over HTTP. The is the umbrella JIRA for
> the tasks.
--
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
