[ https://issues.apache.org/jira/browse/ARROW-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906345#comment-16906345 ]
Micah Kornfield commented on ARROW-6206: ---------------------------------------- "is there a charter for what java usecases will be supported, and THEN, what among these items will leverage NIO, and what among these can use pure heap implementations of objects exclusively?" I don't fully understand this question. My best attempt to answer it below: The system property is needed because we use Netty as an off-heap memory allocator, this could potentially be replaced with something JNI based. The core of the current Java implementation is off-heap memory. If you have specific requirements/use-cases in mind discussing dev@ or user@ mailing list is probably the way to go. Could you provide a link to the text you quoted I'd be interested in reading it. > [Java][Docs] Document environment variables/java properties > ----------------------------------------------------------- > > Key: ARROW-6206 > URL: https://issues.apache.org/jira/browse/ARROW-6206 > Project: Apache Arrow > Issue Type: Improvement > Components: Documentation, Java > Reporter: Micah Kornfield > Priority: Major > > Specifically, "-Dio.netty.tryReflectionSetAccessible=true" for JVMs >= 9 and > BoundsChecking/NullChecking for get. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)