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

Tim Sell commented on HBASE-697:
--------------------------------

I've been working on this.
There's a lot of things to update.

Exposing timestamps for cells.
  Change all the get functions to return TCell instead of Bytes and list<Bytes>.
  A TCell would be the thrift version of a Cell. Just as ColumnDescriptor is to 
HColumnDescriptor.
  with a value and a timestamp field.

Updating to new thrift versions
  Requires the ArrayList's and AbstractMap's to be List and Map. 
  Also the newest libthrift.jar would need to be replaced.

isEnabled, disable enable functions
  Add isTableEnabled function.
  Add enable and disableTable functions. So that a table can actually be 
deleted.

Fix the examples/thrift/DemoClient.java to match all the changes.

Expose more stuff with RegionDescriptor.
  Add endKey, id, name and version.
  I'm inclined that this should be changed to be called TRegionInfo (to match 
the Hbase class RegionInfo)

What about the put functions?
  The HTable as per 0.2 does not have put, they must be done through a 
BatchUpdate.
  The thrift equivalent is mutationRows(table, row, mutations) 
  Do we still want the put functions? Or remove them to match the api?
  They are less cumbersome, they create a BatchUpdate anyway with just a single 
put.

I wanted to have a patch to pick at today, but I ran out of time.
So comments on just the above?



> thrift idl needs update/edit to match new 0.2 API (and to fix bugs)
> -------------------------------------------------------------------
>
>                 Key: HBASE-697
>                 URL: https://issues.apache.org/jira/browse/HBASE-697
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.2.0
>            Reporter: stack
>            Assignee: Bryan Duxbury
>             Fix For: 0.2.1
>
>         Attachments: hbase-timestamps.patch
>
>
> Talking w/ Bryan, moving this out of the way of the 0.2.0 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to