[
https://issues.apache.org/jira/browse/ARROW-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906033#comment-16906033
]
Jim Northrup commented on ARROW-6206:
-------------------------------------
NIO is not going to go away, and java is not going to stop harboring
unreproducable NIO bugs.
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?
the utilities should abandon all hope of stability or useful benchmarks while
there is a NIO component in a piece of code. the oracle engineers this year
are certainly not on the same page as the jdk8 team, or the jdk6 team.
Unsafe/NIO usecases number about 2:
if you're utilizing mmap files to minimize page faults, go there.
if you're talking to crossplatform structs and mailboxes, you have no choice.
if you're squirreling away heap objects using something greater than the -Xmx
setting, you should probably engineer it through mmap file access instead of
using native handles directly, this is extremely unstable in my experience.
> [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)
