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

Colin Patrick McCabe commented on HDFS-6994:
--------------------------------------------

Hi [~decster], that is an interesting idea.  I feel a bit confused about how it 
would save effort, though.  It seems like you're just reimplementing JNI, 
right?  The hassles in JNI are converting between Java and C types, and dealing 
with method signatures and exceptions.  But you have all those same hassles 
when you are making RPCs via JSON.  Plus you have the additional hassle of 
writing a JSON interface for any functionality you want to call, whereas JNI 
can just call any Java function without modifying the Java code.

I guess one nice thing is that you wouldn't have to deal with the Java server 
being attached to the same process as your test process.  But you could get 
that same benefit by calling fork() before calling the JNI functions.

> libhdfs3 - A native C/C++ HDFS client
> -------------------------------------
>
>                 Key: HDFS-6994
>                 URL: https://issues.apache.org/jira/browse/HDFS-6994
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: hdfs-client
>            Reporter: Zhanwei Wang
>            Assignee: Zhanwei Wang
>         Attachments: HDFS-6994-rpc-8.patch, HDFS-6994.patch
>
>
> Hi All
> I just got the permission to open source libhdfs3, which is a native C/C++ 
> HDFS client based on Hadoop RPC protocol and HDFS Data Transfer Protocol.
> libhdfs3 provide the libhdfs style C interface and a C++ interface. Support 
> both HADOOP RPC version 8 and 9. Support Namenode HA and Kerberos 
> authentication.
> libhdfs3 is currently used by HAWQ of Pivotal
> I'd like to integrate libhdfs3 into HDFS source code to benefit others.
> You can find libhdfs3 code from github
> https://github.com/PivotalRD/libhdfs3
> http://pivotalrd.github.io/libhdfs3/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to