gabotechs commented on issue #8938: URL: https://github.com/apache/arrow-rs/issues/8938#issuecomment-3702263749
IMO a solution similar to the one in the Arrow C++ implementation has very good chances to be a proper long term solution to this https://arrow.apache.org/docs/cpp/memory.html#memory-pools. There, a memory pool is not optional, and rather than passively tracking the buffer allocations with a separate mechanism, is the memory pool itself the one responsible for allocating/deallocating Arrow buffers. Not sure if the C++ Arrow implementation can be considered the "canonical one", but it definitely seems the most advanced and mature one, so following their lead might be a good path forward -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
