lidavidm commented on PR #36211: URL: https://github.com/apache/arrow/pull/36211#issuecomment-1625906803
We would love to be more agile with releases. However, it takes quite a bit of maintainer effort. Help is welcome. @danepitkin was exploring if reflection could help. If you have ideas on how exactly that could work, that may be useful. I'm not familiar with why the code is structured like this, other than performance (but I'm not aware of benchmarks for this). `arrow-memory-unsafe` has not received as much usage, in my estimation, because `netty` was for a long time the only implementation and is still the 'default' in effect. Also, if your application also uses Netty, the `unsafe` implementation is not aware of memory allocated by Netty and vice versa (may have to tweak the JVM native memory limit). -- 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]
