[ https://issues.apache.org/jira/browse/HBASE-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903511#action_12903511 ]
Jean-Daniel Cryans commented on HBASE-1744: ------------------------------------------- I don't know if it's on your list Lars, but it would be nice when opening scanners to be able to pass a scanner caching value. This would make more sense than having to set a default value in the configuration to make scanning faster, and it would play nice with numRows of getScannerRows. > 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: Tim Sell > Fix For: 0.90.0 > > Attachments: Hbase.thrift, 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.