You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bob Copeland (Commented) (JIRA)" <ji...@apache.org> on 2011/10/05 23:48:31 UTC
[jira] [Commented] (HBASE-1744) Thrift server to match the new java
api.
[ https://issues.apache.org/jira/browse/HBASE-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121512#comment-13121512 ]
Bob Copeland commented on HBASE-1744:
-------------------------------------
Hi,
I put some fixes for the above issues Ted Yu noted and another fix in my git tree here (will send Tim S. a pull request in a sec):
http://github.com/bcopeland/hbase-thrift
The other fix was to allow timeRange to be null in scannerOpen's TScan.
(I work on a small python library that wraps the thrift API. I just forward ported it to thrift2 today and these were the first issues to pop up.)
> Thrift server to match the new java api.
> ----------------------------------------
>
> Key: HBASE-1744
> URL: https://issues.apache.org/jira/browse/HBASE-1744
> Project: HBase
> Issue Type: Improvement
> Components: thrift
> Reporter: Tim Sell
> Assignee: Lars Francke
> Priority: Critical
> Fix For: 0.94.0
>
> Attachments: HBASE-1744.2.patch, HBASE-1744.3.patch, HBASE-1744.preview.1.patch, thriftexperiment.patch
>
>
> This mutateRows, etc.. is a little confusing compared to the new cleaner java client.
> Thinking of ways to make a thrift client that is just as elegant. something like:
> void put(1:Bytes table, 2:TPut put) throws (1:IOError io)
> with:
> struct TColumn {
> 1:Bytes family,
> 2:Bytes qualifier,
> 3:i64 timestamp
> }
> struct TPut {
> 1:Bytes row,
> 2:map<TColumn, Bytes> values
> }
> This creates more verbose rpc than if the columns in TPut were just map<Bytes, map<Bytes, Bytes>>, but that is harder to fit timestamps into and still be intuitive from say python.
> Presumably the goal of a thrift gateway is to be easy first.
--
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