[
https://issues.apache.org/jira/browse/HBASE-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140735#comment-16140735
]
stack commented on HBASE-10944:
-------------------------------
We can resolve this now until someone proves otherwise? And then the parent
too? [~ram_krish]? Thanks for starting up HBASE-18649, the purge of kv from mr.
Should this be a 2.0 project? Should it block the resolution of this parent
issue?
We should file an issue to plumb through an alternate Cell implementation.
Could even mark it beginner. We could start collecting info on what the new
Cell should be like.
Do we need to do the thing [~anoop.hbase] suggested above +1'd by [~chia7712]?,
i.e.: " getBuffer () exposes that buffer. This is heavily used by tests. May be
we should not expose it public but for test ability exposing getBuffer() may be
ok." ... before we close this?
This long running project is coming to an end. Sweet.
> Remove all kv.getBuffer() and kv.getRow() references existing in the code
> -------------------------------------------------------------------------
>
> Key: HBASE-10944
> URL: https://issues.apache.org/jira/browse/HBASE-10944
> Project: HBase
> Issue Type: Sub-task
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 1.5.0, 2.0.0-alpha-3
>
>
> kv.getRow() and kv.getBuffers() are still used in places to form key byte[]
> and row byte[]. Removing all such instances including testcases will make
> the usage of Cell complete.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
