[
https://issues.apache.org/jira/browse/ARROW-14328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Wujciak-Jens updated ARROW-14328:
---------------------------------------
Summary: [Java] Request for enhancements to BufferAllocator.close() (was:
Request for enhancements to BufferAllocator.close())
> [Java] Request for enhancements to BufferAllocator.close()
> ----------------------------------------------------------
>
> Key: ARROW-14328
> URL: https://issues.apache.org/jira/browse/ARROW-14328
> Project: Apache Arrow
> Issue Type: Wish
> Components: Java
> Reporter: Talia Trilling
> Priority: Major
>
> We are using Arrow in a production environment and running into some issues
> with memory allocation. Specifically, we would like to be able to call
> `BufferAllocator.close()` and have that clean up the allocated memory even if
> there are existing data objects using it, rather than the method throwing an
> exception upon seeing that the allocator is still in use. Are there any plans
> to add support for releasing memory on demand?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
