hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (HBASE-1744) Thrift server to match the new java api.
Date Mon, 30 Nov 2009 02:31:20 GMT

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

stack edited comment on HBASE-1744 at 11/30/09 2:31 AM:
--------------------------------------------------------

Yeah, what Andrew says.  We would deprecate current thrift API in 0.21   The new API would
exist at same time but under contrib. as distinct software. The new API does not have to support
or relate to the old (IMO). If a do-over from scratch makes sense, go for it (IMO). I would
suggest modeling the java API if that will work    Good stuff

      was (Author: stack):
    Yeah, what says.  We would deprecate current thrift API in 0.21   The new API would exist
at same time but under contrib. The new API does not have to support or relate to the old.
If a do over from scratch makes sense go for it. Would suggest modelling the java API if that
will work    Good stuff
  
> Thrift server to match the new java api.
> ----------------------------------------
>
>                 Key: HBASE-1744
>                 URL: https://issues.apache.org/jira/browse/HBASE-1744
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: thrift
>            Reporter: Tim Sell
>            Assignee: Tim Sell
>             Fix For: 0.21.0
>
>         Attachments: 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message