MINOR: Bump com.squareup.okio:okio-jvm from 3.17.0 to 3.18.2 (#1295) Bumps [com.squareup.okio:okio-jvm](https://github.com/lysine-dev/okio) from 3.17.0 to 3.18.2. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lysine-dev/okio/blob/main/CHANGELOG.md">com.squareup.okio:okio-jvm's changelog</a>.</em></p> <blockquote> <h2>Version 3.18.2</h2> <p><em>2026-09-04</em></p> <ul> <li>Fix: Don't change behavior of base64-encoding. We introduced a bug in Okio 3.18.1 that caused base64 strings to be encoded without padding, even though the previous and expected behavior is to encode such strings with padding (<code>=</code> characters). The bug impacts callers who compiled against Okio releases <code>< 3.18.0</code>, and executed on Okio releases <code>>= 3.18</code>.</li> </ul> <h2>Version 3.18.1</h2> <p><em>2026-07-28</em></p> <ul> <li>Fix: Restore binary-compatibility with Okio 3.17.x for Kotlin/Native users. When we introduced the new <code>base64()</code> function, we inadvertently changed the binary signature! Ugh! This is now fixed and we've automated binary-compatibility checking for Kotlin/Native going forward.</li> </ul> <h2>Version 3.18.0</h2> <p><em>2026-07-21</em></p> <ul> <li>Fix: Use wide character APIs to better support of non-UTF-8 filesystems on Windows.</li> <li>Fix: Don't crash in <code>AssetFileSystem.exists()</code> when the underlying storage throws a <code>FileNotFoundException</code>.</li> <li>Fix: Load WASI paths relative to their <code>preopen</code>. The platform behavior recently changed in NodeJS, causing our <code>WasiFileSystem</code> to be unable to access files!</li> <li>New: Optionally ignore whitespace when decoding hexadecimal.</li> <li>New: Optionally omit padding when encoding Base64.</li> <li>New: <code>BufferedSource.readUInt()</code>, <code>BufferedSink.writeUInt()</code>, and similar functions for <code>UByte</code>, <code>UShort</code> and <code>ULong</code>. Also add support for unsigned and little-endian.</li> <li>New: <code>BufferedSink.utf8Appendable()</code>. Use this to adapt an Okio sink to an <code>Appendable</code>.</li> <li>New: <code>Source.limit()</code> returns a wrapped source with a strict limit on how many bytes are returned.</li> <li>New: <code>ByteString.equals(other, constantTime)</code> for subtle defense against timing attacks.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lysine-dev/okio/commit/9403a094ac98d5a6ba8bad4ec3301399796fad67"><code>9403a09</code></a> Prepare for release 3.18.2.</li> <li><a href="https://github.com/lysine-dev/okio/commit/5a1c1538b13cf55897d33c05b2fe2e5e2cdeef53"><code>5a1c153</code></a> Fix an unintended behavior change with base64 padding (<a href="https://redirect.github.com/lysine-dev/okio/issues/1869">#1869</a>)</li> <li><a href="https://github.com/lysine-dev/okio/commit/9f564fd76310120e35b4ffb94b62d6ab2a26207d"><code>9f564fd</code></a> Prepare for release 3.18.1.</li> <li><a href="https://github.com/lysine-dev/okio/commit/531cf07b8ebe140d85448efd6ddff062c13ef317"><code>531cf07</code></a> Hide some accidentally public symbols (<a href="https://redirect.github.com/lysine-dev/okio/issues/1839">#1839</a>)</li> <li><a href="https://github.com/lysine-dev/okio/commit/e7ef43d4d5bd421a51daee9d81ed742a702d0675"><code>e7ef43d</code></a> Update GitHub Actions for new secrets and branch (<a href="https://redirect.github.com/lysine-dev/okio/issues/1840">#1840</a>)</li> <li><a href="https://github.com/lysine-dev/okio/commit/a6730de231a0747359e220eb4b5546a829510d3d"><code>a6730de</code></a> Start enforcing binary compatibility for Kotlin/Native (<a href="https://redirect.github.com/lysine-dev/okio/issues/1838">#1838</a>)</li> <li><a href="https://github.com/lysine-dev/okio/commit/e75a7e9e7fe144ea74baf3e4acd4f2df0a0d0cc0"><code>e75a7e9</code></a> Update dependency com.android.tools.build:gradle to v9.3.1 (<a href="https://redirect.github.com/lysine-dev/okio/issues/1836">#1836</a>)</li> <li><a href="https://github.com/lysine-dev/okio/commit/9d21d5cba334fce36d3316f421d7adcd3fb7ef93"><code>9d21d5c</code></a> Fix interchanged docs links for 1.x and 2.x API (<a href="https://redirect.github.com/lysine-dev/okio/issues/1835">#1835</a>)</li> <li><a href="https://github.com/lysine-dev/okio/commit/bff1dffe5f90e9546b494d4693291a8f72cb07b4"><code>bff1dff</code></a> Track new docs locations from Dokka v2 (<a href="https://redirect.github.com/lysine-dev/okio/issues/1833">#1833</a>)</li> <li><a href="https://github.com/lysine-dev/okio/commit/3b16d9b9dfe6b27ae198a00b7b6d45dc162cddcf"><code>3b16d9b</code></a> Grant write permission to the publish-website action (<a href="https://redirect.github.com/lysine-dev/okio/issues/1832">#1832</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lysine-dev/okio/compare/parent-3.17.0...parent-3.18.2">compare view</a></li> </ul> </details> <br /> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The following guides explain the fundamental data structures used in the Java implementation of Apache Arrow.
Generated javadoc documentation is available here.
Refer to Building Apache Arrow for documentation of environment setup and build instructions.
Arrow uses Google's Flatbuffers to transport metadata. The java version of the library requires the generated flatbuffer classes can only be used with the same version that generated them. Arrow packages a version of the arrow-vector module that shades flatbuffers and arrow-format into a single JAR. Using the classifier “shade-format-flatbuffers” in your pom.xml will make use of this JAR, you can then exclude/resolve the original dependency to a version of your choosing.
$ flatc --version flatc version 25.1.24 $ grep "dep.fbs.version" pom.xml <dep.fbs.version>25.1.24</dep.fbs.version>
cd $ARROW_HOME # remove the existing files rm -rf format/src # regenerate from the .fbs files flatc --java -o format/src/main/java arrow-format/*.fbs # prepend license header mvn spotless:apply -pl :arrow-format
There are several system/environmental variables that users can configure. These trade off safety (they turn off checking) for speed. Typically they are only used in production settings after the code has been thoroughly tested without using them.
Bounds Checking for memory accesses: Bounds checking is on by default. You can disable it by setting either the system property(arrow.enable_unsafe_memory_access) or the environmental variable (ARROW_ENABLE_UNSAFE_MEMORY_ACCESS) to true. When both the system property and the environmental variable are set, the system property takes precedence.
null checking for gets: ValueVector get methods (not getObject) methods by default verify the slot is not null. You can disable it by setting either the system property(arrow.enable_null_check_for_get) or the environmental variable (ARROW_ENABLE_NULL_CHECK_FOR_GET) to false. When both the system property and the environmental variable are set, the system property takes precedence.
-Dio.netty.tryReflectionSetAccessible=true should be set. This fixes java.lang.UnsupportedOperationException: sun.misc.Unsafe or java.nio.DirectByteBuffer.(long, int) not available. thrown by Netty.StructVector enable -Darrow.struct.conflict.policy=CONFLICT_APPEND. Duplicate fields are ignored (CONFLICT_REPLACE) by default and overwritten. To support different policies for conflicting or duplicate fields set this JVM flag or use the correct static constructor methods for StructVectors.Arrow Java follows the Google Java Style Guide with the following differences:
NoFinalizer, OverloadMethodsDeclarationOrder, and VariableDeclarationUsageDistance due to the existing code base. These rules should be followed when possible.Refer to checkstyle.xml for rule specifics.
When running tests, Arrow Java uses the Logback logger with SLF4J. By default, it uses the logback.xml present in the corresponding module's src/test/resources directory, which has the default log level set to INFO. Arrow Java can be built with an alternate logback configuration file using the following command run in the project root directory:
mvn -Dlogback.configurationFile=file:<path-of-logback-file>
See Logback Configuration for more details.
Integration tests which require more time or more memory can be run by activating the integration-tests profile. This activates the Maven Failsafe plugin and any class prefixed with IT will be run during the testing phase. The integration tests currently require a larger amount of memory (>4GB) and time to complete. To activate the profile:
mvn -Pintegration-tests <rest of mvn arguments>