[
https://issues.apache.org/jira/browse/HBASE-13916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589928#comment-14589928
]
stack commented on HBASE-13916:
-------------------------------
Patch looks good.
Why BBUtils have ref to MBB?
import org.apache.hadoop.hbase.nio.MultiByteBuffer;
getVLong takes a MBB but it looks like it could take a BB?
Can fix on commit.
Also, remove this sentence on commit (This MBB looks generic, useable perhaps
by more than HFileBlock): "This has to be used when an
36 * HFileBlock's data is split across multiple byte buffers and we don't
want copy them to single
37 * for serving cells out of it. "
+1
> Create MultiByteBuffer
> ----------------------
>
> Key: HBASE-13916
> URL: https://issues.apache.org/jira/browse/HBASE-13916
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver, Scanners
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Fix For: 2.0.0
>
> Attachments: HBASE-13916.patch, HBASE-13916_V2.patch,
> HBASE-13916_V3.patch
>
>
> This is an aggregation of N ByteBuffers. The block when served directly by
> block cache buckets memory, we have the block data split across multiple byte
> buffers. This aggregate type (like ByteBuffer) will serve the HFileBlock data.
> This jira wil just provide the new data structure
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
