[
https://issues.apache.org/jira/browse/HDFS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100978#comment-13100978
]
Alejandro Abdelnur commented on HDFS-2316:
------------------------------------------
@Todd, well the problem here is that we are overloading the use of a PORT for a
functionality that requires the whole domain of the namespace (in HFDS we don't
have special dirs like /dev). I'd be OK with a different port then.
@Sanjay, the in-direction for writes it would mean that we moving away from a
the REST protocol, which is a well understood and known way of interacting with
resources. I think there a big value in having a full REST API like Hoop has
today.
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
