[
https://issues.apache.org/jira/browse/HBASE-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901147#comment-13901147
]
ramkrishna.s.vasudevan commented on HBASE-7320:
-----------------------------------------------
bq.What about when the Cell is a facade over an onheap block? Here again you
could return the Cell overhead and hope the block is being accounted some other
way. What if the Cell row, family, qualifier, type, and ts – i.e. the 'key' –
are onheap and the data offheap? And so on
I like your explanation. Fine with moving to CellUtil then. So CellUtil would
be talking with a factory that knows how the cell was created right? That
would internally know what was the heapsize?
Ok one basic question :), may sound silly. So we are agreeing to change the
KeyValue format as mentioned in this blog, for eg,
http://blog.cloudera.com/blog/2012/06/hbase-io-hfile-input-output/
and various sources that talks about our KeyValue format. Or to say
keyvalueformat may be different?
bq.What if the Cell row, family, qualifier, type, and ts – i.e. the 'key'
Though we may call this combination as key, the way we form this combination
may vary.
Sorry if am asking too many questions and going off track. am just trying to
ensure that we all are same page or atleast am on the same page.
> Remove KeyValue.getBuffer()
> ---------------------------
>
> 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)
