You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Rok Mihevc (Jira)" <ji...@apache.org> on 2023/01/11 07:07:01 UTC
[jira] [Updated] (ARROW-19) C++: Externalize memory allocations and add a MemoryPool abstract interface to builder classes
[ https://issues.apache.org/jira/browse/ARROW-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rok Mihevc updated ARROW-19:
----------------------------
External issue URL: https://github.com/apache/arrow/issues/15356
> C++: Externalize memory allocations and add a MemoryPool abstract interface to builder classes
> ----------------------------------------------------------------------------------------------
>
> Key: ARROW-19
> URL: https://issues.apache.org/jira/browse/ARROW-19
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Priority: Major
> Fix For: 0.1.0
>
>
> Currently memory allocations in the C++ implementation are all internal / self-contained, but in practice the array builders will need to integrate with some other memory allocator / tracker.
> I'll define a basic abstract memory pool interface and add an example default implementation (with a resizable arrow::Buffer subclass that requests memory from the pool) with all memory managed internally.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)