[
https://issues.apache.org/jira/browse/HBASE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576709#action_12576709
]
Bryan Duxbury commented on HBASE-430:
-------------------------------------
I have a simple implementation for the RowResult class itself already. It'll be
pretty easy to use from a consumption standpoint (implements Map<Text, Cell>).
However, if I change HScannerInterface#next from boolean(HStoreKey,
SortedMap<Text, byte[]>) to RowResult(), there will be far-reaching changes
throughout the code. This is because all scanners everywhere, including the
internal ones used in the region server, implement HScannerInterface at some
point.
Overall I don't think it's going to be a challenging change, beyond the fact
that all the mechanics of advancing scanners is pretty hairy.
> 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
> Priority: Minor
>
> 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.
