[
https://issues.apache.org/jira/browse/HDFS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453515#comment-13453515
]
Suresh Srinivas commented on HDFS-2631:
---------------------------------------
bq. It's not clear, often having it unset means people don't know what to set
it to, and trunk issues are set to 3.0. For this jira the affects version was
set to 3.0 but w/o a target version, then the affects version was unset, then
the fix version was set to 2.0.3-alpha when it was committed, then the fix
version was changed 3.0 today, so it was hard to see where it was going.
If you mean it is hard to understand what the intended target is, I sort of see
that. But following the changes happening in jira etc. should not be an issue.
> Add optional libwebhdfs support to fuse-dfs
> -------------------------------------------
>
> Key: HDFS-2631
> URL: https://issues.apache.org/jira/browse/HDFS-2631
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: fuse-dfs, webhdfs
> Reporter: Eli Collins
> Assignee: Jing Zhao
> Attachments: HDFS-2631.1.patch, HDFS-2631.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
