You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2022/01/31 10:17:00 UTC
[jira] [Resolved] (ARROW-15374) [C++][FlightRPC] Add support for alternative MemoryManagers
[ https://issues.apache.org/jira/browse/ARROW-15374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Pitrou resolved ARROW-15374.
------------------------------------
Fix Version/s: 7.0.0
Resolution: Fixed
Issue resolved by pull request 12239
[https://github.com/apache/arrow/pull/12239]
> [C++][FlightRPC] Add support for alternative MemoryManagers
> -----------------------------------------------------------
>
> Key: ARROW-15374
> URL: https://issues.apache.org/jira/browse/ARROW-15374
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, FlightRPC
> Reporter: David Li
> Assignee: David Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 7.0.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> We should add support for sending/receiving data using a non-standard allocator, given that:
> * the plan is to support UCX as a backend to Flight,
> * UCX can manage non-CPU memory,
> * the existing Device/MemoryManager API handles this case,
> We should find some way to ensure we fully reflect UCX's capabilities to Flight users. Furthermore, we should integrate the MemoryManager and Flight APIs so that Flight user code should not _have_ to worry about whether their backend supports this or not. (That means that for gRPC, we should do the copy for the user.)
> As part of this, we should extend the Flight benchmark to test this case so we also have a baseline.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)