-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARROW-5412: [Integration] Add Java option for netty reflection #4522
ARROW-5412: [Integration] Add Java option for netty reflection #4522
Conversation
…ntegration test command
@pravindra could you verify that this is correct for running integration tests with JDK 9 and above? |
@BryanCutler are the tests not part of CI? I am wondering why they did not fail with the ARROW-3191 changes. |
@praveenbingo CI uses JDK 8, which does not need this conf - I verified this locally too. When running integration tests locally with JDK 9 or higher, it will fail due to this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BryanCutler This resolves the issue on my machine (oracle JDK11). Thanks!
merged to master |
using oracle jdk12 i get Exception in thread "main" java.lang.UnsupportedOperationException: sun.misc.Unsafe or java.nio.DirectByteBuffer.(long, int) not available my pom includes
|
@jnorthrup I created https://issues.apache.org/jira/browse/ARROW-6206 to track documenting this for consumers of the Java library. I don't think the library should be automatically setting the property, but if you have feeling on this, feel free to discuss on the Arrow Dev mailing list. |
@emkornfield im unclear on the priority to use NIO directbytebuffers at this time, if the goal is not to explicitly document and take advantage of memory map files, and or provide an optional off-heap option. for writing records to disk serially, NIO is killing a fly with a sledge-hammer and opens up the package to enormous bug surface area in the unmentionables of misc.unsafe. since I am exclusively interacting with ways to get jdbc to a file format that python can use I should be unencumbered by NIO/netty instabilities. wrt setting properties, i have no opinion. i set the parameter in my jdbc client in the hopes that it fixes a temporary speedbump and the property will not matter if and when the problem goes away.. |
After ARROW-3191, Java requires the property
io.netty.tryReflectionSetAccessible
to be set totrue
for JDK >= 9. This is already in the root POM, but causes integration tests to fail. This adds the property and an option to the Java command when running integration tests.