[
https://issues.apache.org/jira/browse/HBASE-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881472#comment-13881472
]
Lars Hofhansl commented on HBASE-7320:
--------------------------------------
Even better, when're done many of these array copies can go away as we can just
make a new Cell and point it to the existing array if we do not change them.
The next part is to get rid of the timestamp array API completely.
After that, I think, is to writeTo/readFrom files. The writing side might be
simple as long we keep the format, in that case the reading side might not have
to change at all (it is still OK to back a Cell by a single byte[])
Big parts are: ScanQueryMatcher, which dissects the KV itself, and all the
comparators in KeyValue itself.
> Replace calls to KeyValue.getBuffer with appropropriate calls to getRowArray,
> getFamilyArray(), getQualifierArray, and getValueArray
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7320
> URL: https://issues.apache.org/jira/browse/HBASE-7320
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: stack
> Fix For: 0.99.0
>
> Attachments: 7320-simple.txt
>
>
> In many places this is simple task of just replacing the method name.
> There, however, quite a few places where we assume that:
> # the entire KV is backed by a single byte array
> # the KVs key portion is backed by a single byte array
> Some of those can easily be fixed, others will need their own jiras.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
