imhy opened a new issue, #966:
URL: https://github.com/apache/arrow-java/issues/966
### Describe the bug, including details regarding any error messages,
version, and platform.
We are experiencing a compatibility issue when using the arrow-java 17.0.0
library in a Spark application deployed on a Java 1.8 runtime environment.
java.lang.NoSuchMethodError:
java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
at org.apache.arrow.memory.ArrowBuf.setBytes(ArrowBuf.java:847)
at org.apache.arrow.memory.ArrowBuf.setBytes(ArrowBuf.java:899)
at
org.apache.arrow.vector.BaseVariableWidthVector.setSafe(BaseVariableWidthVector.java:1193)
at
org.apache.spark.sql.execution.arrow.StringWriter.setValue(ArrowWriter.scala:256)
at
org.apache.spark.sql.execution.arrow.ArrowFieldWriter.write(ArrowWriter.scala:135)
at
org.apache.spark.sql.execution.arrow.ArrowWriter.write(ArrowWriter.scala:100)
The error indicates that the arrow-java JAR file contains bytecode that
references the ByteBuffer.position(int)
method with a return type of Ljava/nio/ByteBuffer.
This specific method signature was introduced in JDK 9 as part of the
covariance changes in ByteBuffer.
In JDK 8, the same method returns Ljava/nio/Buffer.
Seems library being compiled with a newer JDK (9 or above)
without specifying the correct cross-compilation flags (-release or
-bootclasspath).
Without these flags, the compiler uses its own (newer) API signatures,
making the resulting bytecode incompatible with older JVMs.
It is possible comple library with proper flags and put it to maven
repository?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
