[
https://issues.apache.org/jira/browse/HBASE-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated HBASE-13614:
-------------------------------------------
Attachment: HBASE-13614_1.patch
Just a minor change in HFileBlockIndex while loadDataBlockWithScanInfo().
We cannot have the nextIndexedKey as instance level because the index reader is
once per reader and not once per scanner.
Also the nextIndexKey also acts as an reference to the
HConstants.NO_INDEXED_KEY. So we have more or less covered all the cases and
should be good.
> Avoid temp KeyOnlyKeyValue temp objects creations in read hot path
> ------------------------------------------------------------------
>
> Key: HBASE-13614
> URL: https://issues.apache.org/jira/browse/HBASE-13614
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anoop Sam John
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-13614.patch, HBASE-13614_1.patch
>
>
> As part of HBASE-10800, move to new CellComparator, we are temp creating a
> Cell out of byte[]s so that the Comparator can compare. In read hot path, we
> can try minimize the object creations. The parent Jira added some such cases,
> which we can solve. This Jira will solve all such cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
