You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Todd Lipcon (Commented) (JIRA)" <ji...@apache.org> on 2012/04/17 04:06:18 UTC
[jira] [Commented] (HDFS-2631) Rewrite fuse-dfs to use the webhdfs
protocol
[ https://issues.apache.org/jira/browse/HDFS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255255#comment-13255255 ]
Todd Lipcon commented on HDFS-2631:
-----------------------------------
I'm a little confused: why is this a good idea? Seems like it's likely to end up much slower than the current implementation. I'd prefer it as another option, rather than a "rewrite".
> 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