[
https://issues.apache.org/jira/browse/HBASE-21661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737880#comment-16737880
]
stack commented on HBASE-21661:
-------------------------------
Yeah, could be another issue [~allan163] (there probably is one already). The
mvn proto plugin is nice because it does appropriate binary (Could look into
what it would take when moving thrift to the hbase-connector module?).
+1 on patch (Thanks for the RN and updating the description to make it more
plain what is going on here -- building the case for thrift2 over thrift1).
Thanks [~allan163]
> Provide Thrift2 implementation of Table/Admin
> ---------------------------------------------
>
> Key: HBASE-21661
> URL: https://issues.apache.org/jira/browse/HBASE-21661
> Project: HBase
> Issue Type: Sub-task
> Reporter: Allan Yang
> Assignee: Allan Yang
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-21661.patch, HBASE-21661.v2.patch,
> HBASE-21661.v3.patch, HBASE-21661.v4.patch, HBASE-21661.v5.patch
>
>
> Provide Thrift2 implementation of Table/Admin, making Java user to use thrift
> client more easily(Some environment which can not expose ZK or RS Servers
> directly require thrift or REST protocol even using Java).
> Another Example of this is RemoteHTable and RemoteAdmin, they are REST
> connectors.
> ThriftAdmin/ThriftTable provides another good reason for Java user to use
> thrift2 and not thrift1. Before, they need to convert HBase Get/Put/Scan...
> to TGet/TPut/TScan and construct a thrift client all by themselves. With
> ThriftAdmin/ThriftTable, they can use thrift protocol just like
> HTable/HBaseAdmin. They are just like RemoteHTable/RemoteAdmin for REST
> protocols.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
