dongjoon-hyun edited a comment on issue #24825: [SPARK-27981][CORE] Remove `Illegal reflective access` warning for `java.nio.Bits.unaligned()` in JDK9+ URL: https://github.com/apache/spark/pull/24825#issuecomment-500150865 BTW, the following is not true. From JDK9+, it always shows warnings but print out the first one if there is no `--illegal-access=warn` option. > it only warns if you enable these warnings. Please see the following. ``` $ bin/spark-shell WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.apache.spark.unsafe.Platform (file:/Users/dhyun/PRS/PLATFORM/assembly/target/scala-2.12/jars/spark-unsafe_2.12-3.0.0-SNAPSHOT.jar) to constructor java.nio.DirectByteBuffer(long,int) WARNING: Please consider reporting this to the maintainers of org.apache.spark.unsafe.Platform WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release ``` Before this PR, the first warning was `java.nio.Bits.unaligned()`. And, now, since it's removed by this PR, Java shows the next one, `java.nio.DirectByteBuffer`. In short, if we can remove two warnings from `java.nio.DirectByteBuffer` later, Apache Spark will not show warnings with `Hadoop 3.2` profile at the startup. (Of course, Hive library warnings are totally a different story. We need to find a way for Hive library later, too)
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
