[
https://issues.apache.org/jira/browse/HADOOP-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550265
]
Bryan Duxbury commented on HADOOP-2389:
---------------------------------------
-1 on JSON over sockets. JSON is probably more lightweight than XML in REST,
true, but we'd still need some basic transmission protocol, like REST. However,
I'm not convinced that JSON would make that much of a difference in the long
run, since JSON is a printable format like XML, which means we'd still need to
encode the binary data, which I have to think is the slow part.
+1 on Thrift. It seems to be the best option. If other languages haven't got
Thrift libraries, the solution is to make one or use REST. As more time passes,
Thrift will support more and more languages, so this will be less of a problem.
I've created a draft Thrift spec on the HBase wiki at
http://wiki.apache.org/lucene-hadoop/Hbase/ThriftApi?action=show. Feel free to
make suggestions or changes.
> [hbase] provide multiple language bindings for HBase
> ----------------------------------------------------
>
> Key: HADOOP-2389
> URL: https://issues.apache.org/jira/browse/HADOOP-2389
> Project: Hadoop
> Issue Type: New Feature
> Components: contrib/hbase
> Reporter: Jim Kellerman
> Priority: Minor
>
> There have been a number of requests for multiple language bindings for
> HBase. While there is now a REST interface, this may not be suited for
> high-volume applications. A couple of suggested approaches have been proposed:
> - Provide a Thrift based API (very fast socket based but some of the
> languages are not well supported)
> - Provide a JSON based API over sockets. (faster than REST, but probably
> slower than Thrift)
> Others?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
