You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2016/03/03 23:03:18 UTC
[jira] [Resolved] (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 ]
Wes McKinney resolved ARROW-19.
-------------------------------
Resolution: Fixed
Issue resolved by pull request 8
[https://github.com/apache/arrow/pull/8]
> 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
>
> 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
(v6.3.4#6332)