Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 801E417A6A for ; Fri, 20 Feb 2015 00:28:20 +0000 (UTC) Received: (qmail 56733 invoked by uid 500); 20 Feb 2015 00:28:12 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 56674 invoked by uid 500); 20 Feb 2015 00:28:12 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 56662 invoked by uid 99); 20 Feb 2015 00:28:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Feb 2015 00:28:12 +0000 Date: Fri, 20 Feb 2015 00:28:12 +0000 (UTC) From: "Demai Ni (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-6994) libhdfs3 - A native C/C++ HDFS client MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-6994?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14328= 368#comment-14328368 ]=20 Demai Ni commented on HDFS-6994: -------------------------------- [~wheat9] and [~wangzw], bq. Note that libhdfs3 is always available to the power users =E2=80=93 the= y can check out the code and compile it themselves. Given that I feel that = there is no need rush declaring libhdfs3 is available without stabilizing t= he APIs first. just to chime in here from a user perspective. My team used this libhdfs3 f= or POC since last Oct, and is considering it for our production line. We di= d compile the code ourselves and integrated with our code as [~wheat9] sugg= ested, and tested intensively for the most common APIs: connection, open/cl= ose file, read, seek, etc.. However, to use this code in production, it i= s important for us to have the jira accepted by hdfs community. The reason = is due to general business/development process/guideline. Hence, we really = love to see this jira committed and ok to smaller changes later on API and = error handling. With that said, I am just a user and not expert in hdfs/hadoop area. If the= design or code quality of the jira is not ready yet, certainly it should w= ait. Demai=20 > 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. Suppo= rt both HADOOP RPC version 8 and 9. Support Namenode HA and Kerberos authen= tication. > 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)