[
https://issues.apache.org/jira/browse/PHOENIX-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144364#comment-14144364
]
Lars Hofhansl commented on PHOENIX-1280:
----------------------------------------
A possible solution is to create the column and column families to be projected
as KeyValue objects and use collections with appropriate comparators. That way
the KeyValues passing through the filter do not have to wrapped with
ImmutableBytesPtr just so they can be compare with the existing ones in the
map, they can be used directly instead.
> ColumnProjectionFilter makes too many ImmutableBytesPtrs
> --------------------------------------------------------
>
> Key: PHOENIX-1280
> URL: https://issues.apache.org/jira/browse/PHOENIX-1280
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
>
> While tracing through allocated objects during some queries I find that many
> ImmutableBytesPtr objects are created. One offender is ColumnProjectionFilter
> which first creates the columns to be projected and then while scanning make
> a new ImmutableBytesPtr for each single column that passes through the filter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
