Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion sdk-platform-java/dependencies.txt
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ io.perfmark:perfmark-api,perfmark-api=0.27.0
# Note: This is the google opentelemetry exporter and not the general opentelemetry project
com.google.cloud.opentelemetry:exporter-metrics,google.cloud.opentelemetry=0.36.0
com.google.flogger:flogger,flogger=0.9
org.apache.arrow:arrow-memory-core,arrow=18.3.0
org.apache.arrow:arrow-memory-core,arrow=19.0.0
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Updating arrow-memory-core to a new major version (v19.0.0) in isolation is problematic. Apache Arrow modules (e.g., arrow-vector, arrow-memory-netty) are tightly coupled and must share the same version to maintain binary compatibility; mixing v19.0.0 with v18.x modules will lead to runtime errors such as NoSuchMethodError. Additionally, v19.0.0 introduces breaking API changes (e.g., in BitVectorHelper and MetadataAdapter) and internal changes to ArrowBuf (GH-1038) that may require code updates.

References
  1. Dependency version mismatches suggested by bots should be verified, especially for tightly coupled modules like Apache Arrow where version parity is required for binary compatibility.

dev.cel:cel,dev.cel=0.12.0
com.google.crypto.tink:tink,com.google.crypto.tink=1.21.0
# The follow opentelemetry dependencies have a different version from the opentelemetry-bom
Expand Down
Loading