hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2631) Add optional libwebhdfs support to fuse-dfs
Date Tue, 11 Sep 2012 22:50:07 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453512#comment-13453512

Eli Collins commented on HDFS-2631:

bq. Not sure I understand this comment and why it was hard to follow. When nothing is provided
in these fields is it not intended for trunk?

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
> 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

View raw message