phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5123) Avoid using MappedByteBuffers for server side GROUP BY
Date Thu, 07 Feb 2019 01:30:00 GMT

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

Hudson commented on PHOENIX-5123:
---------------------------------

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #320 (See [https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/320/])
PHOENIX-5123 Avoid using MappedByteBuffers for server side GROUP BY. (larsh: rev 2f985f4839370915f12e440ffffd57bf8ca22866)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/cache/aggcache/SpillFile.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/cache/aggcache/SpillMap.java


> Avoid using MappedByteBuffers for server side GROUP BY
> ------------------------------------------------------
>
>                 Key: PHOENIX-5123
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5123
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0, 4.14.2
>
>         Attachments: 5123-4.x-W.I.P.txt, 5123-4.x-v1.txt
>
>
> Like PHOENIX-5120 but for GROUP BY.
> Solution is a bit more tricky, since outline for sorting the access here is truly random.
> [~apurtell] suggests to perhaps just use a RandomAccessFile for this.
> (I'm not sure that uses under the hood, though)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message