You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Bryan Duxbury (JIRA)" <ji...@apache.org> on 2008/04/03 03:38:24 UTC
[jira] Updated: (HBASE-557) HTable.getRow() should receive
RowResult objects
[ https://issues.apache.org/jira/browse/HBASE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Duxbury updated HBASE-557:
--------------------------------
Attachment: 557.patch
This patch changes the HRegionInterface and HTable to return the right types of objects. All test cases pass.
> HTable.getRow() should receive RowResult objects
> ------------------------------------------------
>
> Key: HBASE-557
> URL: https://issues.apache.org/jira/browse/HBASE-557
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: Bryan Duxbury
> Assignee: Bryan Duxbury
> Priority: Minor
> Fix For: 0.2.0
>
> Attachments: 557.patch
>
>
> Currently still uses HBaseMapWritable of HStoreKeys and Cells. HStoreKeys will have a lot of redundant data (rows and timestamps), and we have to do a transformation when it gets to the client to make it a SortedMap<Text, Cell>. Take advantage of the RowResult class to greatly simplify. Maybe getRow should just return a straight RowResult?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.