[
https://issues.apache.org/jira/browse/ARROW-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668751#comment-16668751
]
Wes McKinney commented on ARROW-3655:
-------------------------------------
I would suggest we start thinking about pooling efforts around function
evaluation in Apache Arrow. For example we already have
{{arrow::compute::FunctionContext}} which has a MemoryPool member
https://github.com/apache/arrow/blob/master/cpp/src/arrow/compute/context.h#L47
> [Gandiva] switch away from default_memory_pool
> ----------------------------------------------
>
> Key: ARROW-3655
> URL: https://issues.apache.org/jira/browse/ARROW-3655
> Project: Apache Arrow
> Issue Type: Task
> Components: Gandiva
> Reporter: Pindikura Ravindra
> Priority: Major
>
> After changes to ARROW-3519, Gandiva uses default_memory_pool for some
> allocations. This needs to be replaced with the pool passed in the Evaluate
> call.
>
> Also, change signatures of all Evaluate APIs (both in project and filter) to
> take a pool argument.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
