[
https://issues.apache.org/jira/browse/PHOENIX-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-1281:
-----------------------------------
Attachment: 1281-v1.txt
Here's a patch.
Saves one allication per row scanned (important for aggregates such as
COUNT/DISTINCT/etc)
> Each MultiKeyValueTuple.setKeyValues creates a new immutable list object
> ------------------------------------------------------------------------
>
> Key: PHOENIX-1281
> URL: https://issues.apache.org/jira/browse/PHOENIX-1281
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Attachments: 1281-v1.txt
>
>
> I looked through all callers of this method, and in each case we have a fresh
> List object anyway, and hence the wrapping is not necessary saving at least
> one new object per row scanned.
> This is probably not really critical, but of a sizable COUNT(\*) or other
> aggregate it still creates lot of unnecessary objects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
