[
https://issues.apache.org/jira/browse/HBASE-12358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187496#comment-14187496
]
stack commented on HBASE-12358:
-------------------------------
bq. HBASE-12224 has nothing in it on why we'd want ByteBuffer readers.
Ignore this question. I can find some justifiation up in HBASE-11425 (a
one-pager would still be a good project I think rather than rely on comments
scattered about JIRA, IMO).
bq. Cell is broke for DBBs because it presumes you can get backing array?
Should we add an hasArray then?
HBASE-11425 explains. Ignore above (except maybe something to hasArray -- for
later)
bq. Or what are the ops we might want to do?
In HBASE-11425, says "...We can handle class by class...." when talking about
getting at arrays. Yeah, we can do that and pull out common cases (like
comparator).
Seems like the BR vs BB still hanging out there.... I like Andrew Purtell
questions up in HBASE-11425....
> Create ByteBuffer backed Cell
> -----------------------------
>
> Key: HBASE-12358
> URL: https://issues.apache.org/jira/browse/HBASE-12358
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver, Scanners
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 2.0.0, 0.99.2
>
> Attachments: HBASE-12358.patch
>
>
> As part of HBASE-12224 we wanted a Cell that is backed by BB. Changing the
> core Cell impl would not be needed as it is used in server only. So we will
> create a BB backed Cell and use it in the Server side read path. This JIRA
> just creates an interface that extends Cell and adds the needed API.
> The getTimeStamp and getTypebyte() can still refer to the original Cell API
> only. The getXXxOffset() and getXXXLength() can also refer to the original
> Cell only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
