java.lang.NoSuchMethodError: java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system
Research direction
Start at the ArrowBuf.setBytes stack frame and the arrow-java 17.0.0 build configuration, then inspect the generated bytecode's use of java.nio.ByteBuffer.position(int) against the Java 8 API. Done means the library can run in the reported Java 1.8 Spark environment without this NoSuchMethodError, with the relevant build or compatibility checks passing.
Written by the indexing model from the issue text.
Description
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?
- Dominant language
- Java
- Stars
- 95
- Forks
- 154
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/arrow-java
-
Type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/arrow-java#1300 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
apache/arrow-java#1261 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/arrow-java#1236 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/arrow-java#1230 ·
-
Type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
apache/arrow-java#1205 ·
All issues in apache/arrow-java
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
[BUG]茶杯方块在取茶时会引发崩溃 Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
1.0.0-alpha2 Type/Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/dpdp-accelerator#272 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
area/frontend
Difficulty 2/5 1-3 hours Newbie friendliness 65/100