Skip to content

chore: update datafusion to 54.0.0#151

Open
jordepic wants to merge 1 commit into
datafusion-contrib:mainfrom
jordepic:datafusion-54
Open

chore: update datafusion to 54.0.0#151
jordepic wants to merge 1 commit into
datafusion-contrib:mainfrom
jordepic:datafusion-54

Conversation

@jordepic

@jordepic jordepic commented Jul 7, 2026

Copy link
Copy Markdown

Updates to datafusion 54.0.0 (same arrow 58.3 line as 53.1.0).

FileFormat and FileSource gained Any as a supertrait with a provided as_any in datafusion 54, so the manual overrides are removed.

FileFormat and FileSource gained Any as a supertrait with a provided
as_any, so the manual overrides are removed.
jordepic added a commit to datafusion-contrib/StreamFusion that referenced this pull request Jul 7, 2026
Arrow 59 needs a DataFusion release that ships it, and none exists yet
(54.0.0, the latest, still pins arrow 58.3; the bump sits unreleased on
DataFusion main). Landing 54 now — same arrow line — absorbs the
DataFusion API churn separately, so the eventual arrow 59 commit shrinks
to the arrow/ptars/fluss pins.

The churn is small: Any became a supertrait of the UDF and file-source
traits with a provided as_any (the manual overrides are deleted), and
SimplifyContext moved to a builder. datafusion-orc has no 54-compatible
rev upstream, so it is pinned to a temporary fork carrying only that
bump, with the upstream PR open
(datafusion-contrib/datafusion-orc#151) —
repoint when it merges, the same retirement path as the fluss fork.

Revisited divergence 16 as its note asks: DataFusion 54's scan path
still registers no memory consumers, so file scans stay un-pool-wired.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant