[
https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703969#action_12703969
]
Alex Newman commented on HBASE-1015:
------------------------------------
I am not exactly sure I understand this issue. We had similar worries as our
shop is <bold>very</bold> c++ biased, and we went with the thrift client. We
now solely write c++ based code and tbh hitting a thrift server local to the
data is faster than falling back to the rpc mechanism anyway. Would it be
enough to write an efficient c++ based thrift server? I would love to see
thrift api be the focus of api development as their are still numerous features
which haven't been moved out of the java api. Anyway, just my two cents, I will
totally help out with any c++ api.
> 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
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 0.21.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.
