[
https://issues.apache.org/jira/browse/HBASE-12023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139472#comment-14139472
]
Lars Hofhansl edited comment on HBASE-12023 at 9/18/14 8:39 PM:
----------------------------------------------------------------
That was my first thought too... However, this relies on the map value being an
ArrayList (otherwise get() is slow). That happens to be the case, but we do not
enforce that anywhere.
It's a shame we cannot get rid of outer iterator. In the vast majority of the
case we only have a single column family anyway, but we have no way to get that
without an iterator.
was (Author: lhofhansl):
That was my first thought too... However, this relies on the map value being an
ArrayList. That happens to be the case, but we do not enforce that anywhere.
It's a shame we cannot get rid of outer iterator. In the vast majority of the
case we only have a single column family anyway, but we have no way to get that
without an iterator.
> HRegion.applyFamilyMapToMemstore creates too many iterator objects...
> ---------------------------------------------------------------------
>
> Key: HBASE-12023
> URL: https://issues.apache.org/jira/browse/HBASE-12023
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.5, 0.94.23
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Minor
> Attachments: HBASE-12023.patch, applyFamilyMapToMemstore (1).tiff
>
>
> for ... loop (creates iterator) inside another for loop. Produces a lot of
> garbage. See attached picture.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
