phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1281) Each MultiKeyValueTuple.setKeyValues creates a new immutable list object
Date Thu, 25 Sep 2014 17:09:34 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147991#comment-14147991
] 

Hudson commented on PHOENIX-1281:
---------------------------------

FAILURE: Integrated in Phoenix | 4.0 | Hadoop2 #165 (See [https://builds.apache.org/job/Phoenix-4.0-hadoop2/165/])
PHOENIX-1281 Each MultiKeyValueTuple.setKeyValues creates a new immutable list object. (larsh:
rev 349d04fda90e5d0e0a080c6ca46693c890dc1046)
* phoenix-core/src/main/java/org/apache/phoenix/schema/tuple/MultiKeyValueTuple.java
* phoenix-core/src/main/java/org/apache/phoenix/coprocessor/ScanRegionObserver.java


> 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
>            Assignee: Lars Hofhansl
>             Fix For: 5.0.0, 4.2, 3.2
>
>         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)

Mime
View raw message