[
https://issues.apache.org/jira/browse/HBASE-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882073#comment-13882073
]
Lars Hofhansl commented on HBASE-7320:
--------------------------------------
bq. Can we change the Cell Interface ex post facto?
Cell has only {{long getTimestamp()}}, so that's clean. I meant removing calls
to getTimestampOffset, etc.
bq. Would the best approach now be to try and implement a new Cell type
altogether?
Maybe, but then we'd have to replace KeyValue everywhere, and the KeyValue type
leaks to the client, so not sure we can do that.
In the end it'd come to the same, either we make a new type, or we fix KeyValue
to be the new type. Either way seems fine.
bq. How you think we fix these Lars?
Need to look at each case individually to see how to fix them. Some are only
printing out the key for example and in that we just print the
row/family/qualifier/timestamp separately.
> 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)
