I'm not sure what the best way to handle this is. Ideally we would use an
alternative that doesn't require setting a property, but I don't know Netty
well enough to make a recommendation. I also want to be careful not to
introduce anything that would hurt performance or cause any other side
effect
Hi Bryan,
Thanks for bringing this up.
+1 for the change.
I am not clear what is the right place to override the jvm property.
It is possible that when we try to override it (possibly in a static
block), the old property value has already been read by netty library.
To avoid this problem, do we n
This sounds reasonable to me. At this point I think having our consumers
have a better experience is more important then library purity concerns
I've had in the past.
Do we need to handle jdk8 as a special case? Do you think it pays to try
to find an alternate library that doesn't require specia
After ARROW-3191 [1], consumers of Arrow Java with a JDK 9 and above are
required to set the JVM property "io.netty.tryReflectionSetAccessible=true"
at startup, each time Arrow code is run, as documented at [2]. Not doing
this will result in the error "java.lang.UnsupportedOperationException:
sun.m
