[
https://issues.apache.org/jira/browse/HDFS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255350#comment-13255350
]
Todd Lipcon commented on HDFS-2631:
-----------------------------------
That seems reasonable. I think it's a given that we need to keep the original
libhdfs for performance. Having a libhdfs-alike that goes over HTTP seems
reasonable enough but not always preferable. To speak to each of the original
points:
bq. Compatibility - allows a single fuse client to work across server versions
We need to address compatibility for clients in general. Our Java client (and
hence libhdfs) need this just as much as fuse.
bq. Works with both WebHDFS and Hoop since they are protocol compatible
I guess this is an advantage, but given that libhdfs already wraps arbitrary
hadoop filesystems, we already have this capability.
bq. Removes the overhead related to libhdfs (forking a jvm)
fuse is a long-running client, so the fork overhead seems minimal. Recent
improvements in libhdfs have also cut out most of the copying overhead.
bq. Makes it easier to support features like security
Perhaps - but libhdfs needs security anyway, so I don't think it buys us much.
> Rewrite fuse-dfs to use the webhdfs protocol
> --------------------------------------------
>
> Key: HDFS-2631
> URL: https://issues.apache.org/jira/browse/HDFS-2631
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: contrib/fuse-dfs
> Reporter: Eli Collins
> Assignee: Jaimin D Jetly
>
> We should port the implementation of fuse-dfs to use the webhdfs protocol.
> This has a number of benefits:
> * Compatibility - allows a single fuse client to work across server versions
> * Works with both WebHDFS and Hoop since they are protocol compatible
> * Removes the overhead related to libhdfs (forking a jvm)
> * Makes it easier to support features like security
--
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
