You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2008/11/26 02:42:44 UTC

[jira] Issue Comment Edited: (HBASE-1015) pure C and C++ client libraries

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

apurtell edited comment on HBASE-1015 at 11/25/08 5:42 PM:
-----------------------------------------------------------------

Could also look at Google's "protocol buffers" for a native binary protocol: http://code.google.com/p/protobuf/
http://code.google.com/p/protobuf-rpc/


      was (Author: apurtell):
    Could also look at Google's "protocol buffers" for a native binary protocol: http://code.google.com/p/protobuf/
  
> pure C and C++ client libraries
> -------------------------------
>
>                 Key: HBASE-1015
>                 URL: https://issues.apache.org/jira/browse/HBASE-1015
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: client
>            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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.