[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867787#comment-13867787 ] Cosmin Lehene commented on HBASE-1015: -- HBASE-9977 suggests a C++ async client and C sync/async wrappers. Given that HBase talks protobuf natively. Is a native wrapper around Thrift still a goal? 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)
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868382#comment-13868382 ] Ted Dunning commented on HBASE-1015: 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? Shouldn't reality be recognized? Shouldn't this be closed as WONT_FIX? 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)
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13556412#comment-13556412 ] Andrew Purtell commented on HBASE-1015: --- bq. I don't think the thrift core makes sense anymore, considering protobuf. I would agree. The embedded thrift servers in the regionservers were an experiment at FB that they've backed away from. THRIFT-1620 is open with no implementation available. bq. I think an HBase client library implemented in C is a mandatory feature for a database approaching 1.0 release. The PB work is not finished. 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. Various discussions I have had about native client usually end with the notion of a Grand Unified Client Project: lighter weight async client, perhaps asynchbase itself or in the mold of it, talking PB to the cluster, with a sync API layered on top. It might be straightforward to build a C++ analogue to asynchbase with std::async (don't know enough about C++11 to say for sure). 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
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13556426#comment-13556426 ] Andrew Purtell commented on HBASE-1015: --- I will throw out there that libhdfs cheats by linking to libjvm.so and pulling in the HDFS client bytecode as engine. I presume we don't want this, but it would be a half measure that stands in for something comprehensive. 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
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13556446#comment-13556446 ] Nick Dimiduk commented on HBASE-1015: - My previous experience with JNI makes me cringe at this prospect. Perhaps a painful baby-step, this would be a baby-step non the less. 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
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13555600#comment-13555600 ] Nick Dimiduk commented on HBASE-1015: - What's happened with this ticket? I don't think the thrift core makes sense anymore, considering protobuf. I think an HBase client library implemented in C is a mandatory feature for a database approaching 1.0 release. 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
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424432#comment-13424432 ] Mikhail Bautin commented on HBASE-1015: --- I think this is now resolved. Here is the C++ HBase client written by Chip Turner at Facebook: https://github.com/facebook/native-cpp-hbase-client 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424436#comment-13424436 ] stack commented on HBASE-1015: -- Mikhail I think this worth an announcement out on the user mailing list? Its great stuff. If you don't want to do it, I will (better if you do it). I added note to refguide and pushed it out. 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424439#comment-13424439 ] Mikhail Bautin commented on HBASE-1015: --- Actually Chip should probably announce this feature himself. I will ask him about it. 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424440#comment-13424440 ] stack commented on HBASE-1015: -- @Mikhail That'd be best for sure. 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424443#comment-13424443 ] Andrew Purtell commented on HBASE-1015: --- I'd be delighted to resolve this issue (excellent!) but just to be sure: Do we want to hold it open as a vehicle for moving the native-cpp-hbase-client code into the HBase tree proper, or no? If the latter, let's resolve. 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[
https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424447#comment-13424447
]
Andrew Purtell commented on HBASE-1015:
---
[~mikhail] Perhaps someone more versed in Thrift and its C++ language support
in particular could say, but can we plug in Thrift's
TSasl{Client,Server}Transport here for authenticated opens and optional wire
encryption?
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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424488#comment-13424488 ] Todd Lipcon commented on HBASE-1015: Hey Andrew. Someone here at Cloudera is working on SASL support for the Thrift C++ bindings, I believe -- at least the client side -- which should be compatible with the Java server. Hopefully we'll post it to THRIFT-1620 in the coming weeks. 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919130#action_12919130 ] skyhyc commented on HBASE-1015: --- Up!!! 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 Fix For: 0.92.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.
[jira] Commented: (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915671#action_12915671 ] skyhyc commented on HBASE-1015: --- No, I just know Hbase provide API for Thrift, but don't know how to use it. 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 Fix For: 0.92.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.
[jira] Commented: (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915226#action_12915226 ] skyhyc commented on HBASE-1015: --- How to use C++ with Hbase?Anybody who would like to give a example? 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 Fix For: 0.92.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.
[jira] Commented: (HBASE-1015) pure C and C++ client libraries
[ https://issues.apache.org/jira/browse/HBASE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12914862#action_12914862 ] stack commented on HBASE-1015: -- @skyhyc Did you put a patch up? I don't see it. 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 Fix For: 0.92.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.
