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

Allen Wittenauer commented on HDFS-6994:
----------------------------------------

bq. (boost as support for older compilers)

I'm very much against boost showing up in Hadoop in any way, shape, or form.  
It's *always* long term pain.  I'd much rather take the short term hit of 
requiring a modern compiler than deal with boost.

bq. I don't have a problem with naming it libhdfs3, but users might wonder what 
libhdfs2 was 

It's actually a bigger support problem:

Alice: "What version of libhdfs are you using?"

Bob: "I'm using v3!"
 
Alice: "Ugh, what version of libhdfs3 are you using?"

...

(I say this as someone who early in their career had to support something 
called AutoInstall3.  It was a nightmare...)

bq. How about libndfs++ as a name?

Ha. I was thinking "what name would I recommend instead?" this morning and came 
up with libhdfs++. :)



> libhdfs3 - A native C/C++ HDFS client
> -------------------------------------
>
>                 Key: HDFS-6994
>                 URL: https://issues.apache.org/jira/browse/HDFS-6994
>             Project: Hadoop HDFS
>          Issue Type: Task
>          Components: hdfs-client
>            Reporter: 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