[
https://issues.apache.org/jira/browse/HBASE-10531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906080#comment-13906080
]
stack commented on HBASE-10531:
-------------------------------
Agree w/ [[email protected]] comment above
What is going on below here? We add an API but then call the old? Shouldn't
we be going the other way? The old calling the new?
{code}
+ public int seekTo(Cell kv) throws IOException {
+ KeyValue keyValue = KeyValueUtil.ensureKeyValue(kv);
+ return seekTo(keyValue.getBuffer(), keyValue.getOffset(),
keyValue.getLength());
+ }
{code}
> Revisit how the key byte[] is passed to HFileScanner.seekTo and reseekTo
> ------------------------------------------------------------------------
>
> Key: HBASE-10531
> URL: https://issues.apache.org/jira/browse/HBASE-10531
> Project: HBase
> Issue Type: Sub-task
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 0.99.0
>
> Attachments: HBASE-10531.patch
>
>
> Currently the byte[] key passed to HFileScanner.seekTo and
> HFileScanner.reseekTo, is a combination of row, cf, qual, type and ts. And
> the caller forms this by using kv.getBuffer, which is actually deprecated.
> So see how this can be achieved considering kv.getBuffer is removed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
