phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PHOENIX-5123) Avoid using MappedByteBuffers for server side GROUP BY
Date Tue, 05 Feb 2019 22:41:00 GMT

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

Lars Hofhansl edited comment on PHOENIX-5123 at 2/5/19 10:40 PM:
-----------------------------------------------------------------

Well... Currently you can't read or write past the buffer, i.e. past the 4k. With my new code
a writer writing more than 4k would corrupt the next page. (Pages are retrieved at offsets
as multiples of 4k)

I think the surrounding code handles that, though. So perhaps is just fine as is.


was (Author: lhofhansl):
Well... Currently you can't read or write past the buffer, i.e. past the 4k. With my new code
a writer writing more than 4k would corrupt the next page. (Pages are retrieved at offsets
as multiples of 4k)

> 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
>            Priority: Major
>         Attachments: 5123-4.x-W.I.P.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