[
https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556423#comment-13556423
]
Nick Dimiduk commented on HBASE-1015:
-------------------------------------
bq. The scope of building a C client is not just the transport, it's also
duplicating or replacing all of the functionality of the fat Java client.
Agreed; I mean the construction of a fully-featured client implementation
available via C, not just transport. I've been out of C/C++ for a number of
years, I'm entirely ignorant on C++11 so I cannot comment on implementation
details. I do know that it's fairly common-place to wrap a C++ library with C
bindings, so that decision can be left up to the implementor.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
