[
https://issues.apache.org/jira/browse/HDFS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143452#comment-13143452
]
Tsz Wo (Nicholas), SZE commented on HDFS-2316:
----------------------------------------------
> gethomedir is required as you don't know where the FS impl creates the home
> dir.
Okay, I can add it to webhdfs.
> The doAs parameter name was chosen to mimic the Java API, real.user is kind
> of confusing, do you mean the proxy user or the doAs user. Plus when doing
> Kerberos you don't use user.name. IMO doAs is a easier not to get confused.
I am fine with using doAs instead of realUser.
BTW, hadoop auth use "user.name". The dot in the middle is different from
other naming convention. How about changing it to username?
> The GET_BLOCK_LOCATIONS private API, how are you differentiating private and
> public APIs?
We will document it and state that it is a private unstable API.
> 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
