[ 
https://issues.apache.org/jira/browse/HBASE-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332986#comment-17332986
 ] 

Itay Bittan commented on HBASE-8818:
------------------------------------

Sorry for asking here, but I couldn't find an answer anywhere else.

I am using HBase 0.94.22 with Python (mainly add/increments rows) and I might 
upgrade to the latest HBase version in the future.

I wonder whether to use Thrift1 or Thrift2 and here is what I understand so far:

+*Thrift1*+

*pros:* 
 * support increments in batch.
 * supported by [HappyBase|https://github.com/python-happybase] which also has 
async Python implementation + batch for increments.

*cons:*
 * older implementation?
 * is it supported in the latest HBase version?
 * slower? (not sure why thrift2 was introduced)

 

+*Thrift2*+

*pros:*
 * new implementation
 * only support for new HBase versions?

*cons:*
 * no Python package, need to use Thrift 
[wrapper|https://github.com/apache/hbase/blob/master/hbase-examples/src/main/python/thrift2/DemoClient.py].
 * Doesn't support multiple increments? (batch)

 

I will appreciate any piece of information to make the best choice, Thanks in 
advance.

 

 

 

> [thrift2] Update Thrift2 to supersede Thrift1 and equal REST
> ------------------------------------------------------------
>
>                 Key: HBASE-8818
>                 URL: https://issues.apache.org/jira/browse/HBASE-8818
>             Project: HBase
>          Issue Type: Umbrella
>          Components: Thrift
>            Reporter: Lars George
>            Assignee: Lars George
>            Priority: Major
>              Labels: thrift2
>         Attachments: HBase Thrift2 Comparison.xlsx
>
>
> This is an umbrella issue, listing all issues from Thrift1 that need to be 
> applied to Thrift2 (those that have only be applied to the former but should 
> be in both), and what else is missing for a fully functional Thrift2 API.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to