hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-430) Performance: Scanners and getRow return maps with duplicate data
Date Wed, 12 Mar 2008 05:44:46 GMT

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

stack commented on HBASE-430:
-----------------------------

Ok on the mapping.  I don't know of a way around the copy. Go ahead and apply I'd say.

> Performance: Scanners and getRow return maps with duplicate data
> ----------------------------------------------------------------
>
>                 Key: HBASE-430
>                 URL: https://issues.apache.org/jira/browse/HBASE-430
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>            Priority: Minor
>         Attachments: 430-v2.patch, 430-v3.patch, 430-v4.patch, 430-v5.patch, 430.patch
>
>
> Right now, whenever we get back multiple cells worth of data at a time, we do so in a
map of HStoreKey->byte[]. This means that there is a duplicated Text row and long timestamp
at the very least between every cell. This is quite a bit wasted. It also means we have to
do a lot of translation every time. 
> We could create a new Writable that contains just one row, one timestamp, and a map of
Text->byte[].

-- 
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