You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Todd Farmer (Jira)" <ji...@apache.org> on 2022/07/12 14:05:03 UTC

[jira] [Assigned] (ARROW-7198) [Java] Allow a user to provide an alternative "chunk" allocator

     [ https://issues.apache.org/jira/browse/ARROW-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Farmer reassigned ARROW-7198:
----------------------------------

    Assignee:     (was: Jacques Nadeau)

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [Java] Allow a user to provide an alternative "chunk" allocator
> ---------------------------------------------------------------
>
>                 Key: ARROW-7198
>                 URL: https://issues.apache.org/jira/browse/ARROW-7198
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: Java
>            Reporter: Jacques Nadeau
>            Priority: Major
>
> Right now, the Arrow Java libraries have two options:
> - Have accounted memory using the Netty allocator.
> - Have unaccounted memory using your own allocator.
> I'd like to add a third option where you can use the existing accounting but decide where the chunks of memory come from.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)