[ https://issues.apache.org/jira/browse/ARROW-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433737#comment-16433737 ]
Antoine Pitrou commented on ARROW-1470: --------------------------------------- Could you explain why this couldn't be solved by having a shared memory-allocating MemoryPool subclass? > [C++] Add BufferAllocator abstract interface > -------------------------------------------- > > Key: ARROW-1470 > URL: https://issues.apache.org/jira/browse/ARROW-1470 > Project: Apache Arrow > Issue Type: New Feature > Components: C++ > Reporter: Wes McKinney > Priority: Major > Fix For: 0.10.0 > > > There are some situations ({{arrow::ipc::SerializeRecordBatch}} where we pass > a {{MemoryPool*}} solely to call {{AllocateBuffer}} using it. This is not as > flexible as it could be, since there are situation where we may wish to > allocate from shared memory instead. > So instead: > {code} > Func(..., BufferAllocator* allocator, ...) { > ... > std::shared_ptr<Buffer> buffer; > RETURN_NOT_OK(allocator->Allocate(nbytes, &buffer)); > ... > } > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)