[ https://issues.apache.org/jira/browse/HBASE-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081208#comment-13081208 ]
Ted Yu commented on HBASE-1744: ------------------------------- Sorry to get back to this so late. I got the following: {code} [INFO] Compilation failure /home/hadoop/hbase/src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftServer.java:[68,19] ThriftServer() has private access in org.apache.hadoop.hbase.thrift2.ThriftServer /home/hadoop/hbase/src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftServer.java:[83,22] cannot find symbol symbol : method isMasterRunning() location: class org.apache.hadoop.hbase.thrift2.ThriftHBaseServiceHandler {code} > 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.92.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. For more information on JIRA, see: http://www.atlassian.com/software/jira