[
https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833077#action_12833077
]
Andrew Purtell commented on HBASE-1015:
---------------------------------------
The intent of this issue is to build a fat client in C, wrap in C++, and have
it talk directly to the master and regionservers without any gateway/connector
process as intermediary. The C++ wrapper would have similar class structure and
API as o.a.h.h.client. No need for any Java except on the servers. No
intermediary to be a potential bottleneck.
The notion has a reasonable argument but it's a lot of work. The rationale for
taking it on has become less convincing over time as the Thrift and REST
connectors have been satisfying enough for users. There was a fair amount of
interest in the 0.19 days but that has waned as far as I can see.
> 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
> Fix For: 0.22.0
>
>
> 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.
