hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-1015) pure C and C++ client libraries
Date Fri, 10 Jan 2014 22:30:55 GMT

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

Andrew Purtell commented on HBASE-1015:
---------------------------------------

bq. Another way to put this is that if nobody cares enough to even put up a patch after 5
years is this issue simply moot?

This issue has been superseded by the use of protobuf in RPCs instead of Thrift and the commit
of the start of a C/C++ client library, see HBASE-9977. Closing this issue in lieu of something
else is fine, but WONTFIX is the incorrect resolution.

> pure C and C++ client libraries
> -------------------------------
>
>                 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
>            Reporter: Andrew Purtell
>            Priority: Minor
>
> 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.1.5#6160)

Mime
View raw message