[ 
https://issues.apache.org/jira/browse/HDFS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133090#comment-13133090
 ] 

Sanjay Radia commented on HDFS-2316:
------------------------------------

Alejandro raised the following 4 issues for discussion:
# rename - should the target path contain the /webhdfs prefix since a client 
app will want to simply take the target path and use it as part of a read 
operation.
# should getStatus return the paths with the /webhdfs prefix
# Why is the scheme of the webhdfs file system  "webhdfs:" and not "http:"
# case sensitivity - make the parameters lower case rather than have the filter 
convert them since pathname and the user name should not be converted.

My initial thoughts are: 
* for 1 and 2: the rename target path and the paths in the filestatus should 
NOT contain contain /webhdfs since /webhdfs is not really part of the 
parameters but a part of the rest api's "headers".
* for scheme - i don't think we should use a prexisting scheme name. Nfs 
community has used webnfs as the scheme for accessing nfs over http.
* I am fine with lower case parameters.
                
> 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
>
>
> 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

        

Reply via email to