phoenix-issues mailing list archives

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

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

Andrew Purtell commented on PHOENIX-5123:
-----------------------------------------

.bq I think in my new code I should add an explicit safety check to not read from or write
past 4k.

Do you? Because now it would be ok. RAF by itself is just backed by the file in the filesystem.
You can do positioned reads and writes of arbitrary length, well at least within constraints
of the underlying filesystem's free space.

> 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