[
https://issues.apache.org/jira/browse/ARROW-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078072#comment-17078072
]
Antoine Pitrou commented on ARROW-8368:
---------------------------------------
> Should it be allowed to move multiple children, as long as they are moved at
> the same time, and the parent is released after?
We should experiment with that in the C++ implementation.
> In the event that children have disjoint internal resources, should there be
> a clarification around moved children having their resources released
> independently?
I don't think so. This is the producer's choice. It may for example use a
single arena for all allocations in the array tree, and only release resources
when all release callbacks have been called.
> [Format] In C interface, clarify resource management for consumers needing
> only a subset of child fields in ArrowArray
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: ARROW-8368
> URL: https://issues.apache.org/jira/browse/ARROW-8368
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Format
> Reporter: Wes McKinney
> Priority: Major
>
> The current implication of the C Interface is that only moving a single child
> out of an ArrowArray is allowed.
> Questions:
> * Should it be allowed to move multiple children, as long as they are moved
> at the same time, and the parent is released after?
> * In the event that children have disjoint internal resources, should there
> be a clarification around moved children having their resources released
> independently?
> See mailing list discussion
> https://lists.apache.org/thread.html/r92b77e0fa7bed384daa377e2178bc8e8ca46103928598050341e40b1%40%3Cdev.arrow.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
