Skip to content
Open
Show file tree
Hide file tree
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
227 changes: 162 additions & 65 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ uuid = { version = "1.18", default-features = false, features = [
"v4",
] }
once_cell = "1.21"
arrow = { version = "57.0", default-features = false }
arrow = { version = "58.1", default-features = false }
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Align Arrow ecosystem versions in workspace deps

Bumping only arrow to 58.1 while leaving arrow-array, arrow-buffer, arrow-schema, and parquet on the 57.x line creates a split Arrow dependency graph. In this commit’s lockfile, lading-capture now pulls arrow 58.1.0 plus arrow-array/-buffer/-schema 57.3.0, so Cargo builds two incompatible Arrow type universes and duplicates compile work; this also means the actual parquet/capture data path remains on 57.x despite the version bump. Please bump the related Arrow crates together (or keep arrow on 57.x) to avoid this skew.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Align Arrow major version with Parquet workspace deps

Updating only arrow to 58.1 while parquet and the direct Arrow component crates remain on 57.x splits the dependency graph into two incompatible Arrow type universes, which increases compile time and can cause type-mismatch friction if code needs to pass types between arrow and parquet::arrow APIs. Fresh evidence in this commit: Cargo.lock now contains both arrow-array/arrow-buffer/arrow-schema 57.3.0 (via parquet and direct deps) and 58.1.0 (via the bumped arrow crate), so the bump does not actually move the parquet/capture path to 58.x.

Useful? React with 👍 / 👎.

parquet = { version = "57.1", default-features = false }
proptest = "1.9"
proptest-derive = { version = "0.7" }
Expand Down
Loading