[
https://issues.apache.org/jira/browse/HDFS-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408228#comment-13408228
]
Colin Patrick McCabe commented on HDFS-2631:
--------------------------------------------
Hi Jaimin,
It's great that you're working on this.
I think it would be best if you kept the existing libhdfs API. That way, users
can easily switch back and forth between the JNI based libhdfs and your
webhdfs-based libhdfs. If you do not do this, all applications will have to be
rewritten, which may limit the number of people who can use your work.
In a similar vein, I think you should avoid changing fuse-dfs in this patch (it
would definitely make it a lot smaller). And if you implement the existing
API, then obviously there's no reason to modify FUSE at all.
Finally, we're using CMake now so you should update your patch to make use of
that. CMake is very straightforward. Let me know if you have any questions or
if you want to see an example CMakeLists.txt.
> 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: webhdfs
> Reporter: Eli Collins
> Assignee: Jaimin D Jetly
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
