You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/12/21 02:47:46 UTC

[jira] [Commented] (HBASE-1015) HBase Native Client Library

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

Sean Busbey commented on HBASE-1015:
------------------------------------

is this effort still ongoing?

is the patch here, or the github pull request ( https://github.com/apache/hbase/pull/1 ) the latest version?

/cc [~eclark]

> HBase Native Client Library
> ---------------------------
>
>                 Key: HBASE-1015
>                 URL: https://issues.apache.org/jira/browse/HBASE-1015
>             Project: HBase
>          Issue Type: New Feature
>          Components: Client
>    Affects Versions: 0.20.6, 1.0.0
>            Reporter: Andrew Purtell
>            Assignee: Aditya Kishore
>            Priority: Minor
>         Attachments: HBASE-1015-HBase-native-client.patch, HBASE-1015-HBase-native-client.patch
>
>
> If via HBASE-794 first class support for talking via Thrift directly to HMaster and HRS is available, then pure C and C++ client libraries are possible. 
> The C client library would wrap a Thrift core. 
> The C++ client library can provide a class hierarchy quite close to o.a.h.h.client and, ideally, identical semantics. It  should be just a wrapper around the C API, for economy.
> Internally to my employer there is a lot of resistance to HBase because many dev teams have a strong C/C++ bias. The real issue however is really client side integration, not a fundamental objection. (What runs server side and how it is managed is a secondary consideration.)



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