hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-1015) HBase Native Client Library
Date Mon, 21 Mar 2016 05:05:26 GMT

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

Sean Busbey commented on HBASE-1015:

last call for concerns with me closing this issue out as obviated by the work in HBASE-14850

> 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

View raw message