Smith-Cruise opened a new pull request, #99: URL: https://github.com/apache/paimon-mosaic/pull/99
Mosaic exposes Arrow arrays, record batches and schemas through its Rust API. Keeping these dependencies on Arrow 58 prevents consumers moving to the Arrow 59 ecosystem, including paimon-rust's DataFusion 55 migration, from sharing the same Rust Arrow types with Mosaic. Upgrade the Rust Arrow dependencies in core, FFI, JNI and CLI to `59`, preserving their existing features. Resolve the workspace's Arrow crates to 59.3.0 in Cargo.lock and refresh the dependency inventories and per-target license reports. The accompanying base64 and num-bigint updates are required by Arrow 59.3.0's dependency constraints. DataFusion 55.0.0 declares Arrow `59.2.0`, which is a caret requirement accepting 59.3.0; see [its dependency definitions](https://github.com/apache/datafusion/blob/55.0.0/Cargo.toml) and [Cargo's version requirement rules](https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#default-requirements). Mosaic's manifests use `59`, allowing consumers to resolve a compatible 59.x version rather than requiring exactly 59.3.0. The public Rust Arrow types move from major version 58 to 59, so Rust consumers passing these types need to align their dependencies. This PR preserves the existing Mosaic file format, C/JNI interface definitions and Java Arrow/Python PyArrow dependency declarations. Other parts of paimon-rust's DataFusion 55 migration remain separate work. Validation: dependency resolution and static diff review only. A temporary dependency-only consumer combining DataFusion 55.0.0 and this Mosaic core resolved all Arrow crates to 59.3.0. No local compilation, Clippy or tests were run. The existing upstream CI will validate Rust builds/tests, C++/Java/Python interoperability, formatting and license inventory checks. This PR remains a draft pending CI validation. -- 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]
