Skip to content

deps: upgrade to DataFusion 55.0 and Arrow/Parquet 59.2 - #2958

Merged
kevinjqliu merged 15 commits into
apache:mainfrom
mbutrovich:df55
Sep 3, 2026
Merged

kevinjqliu merged 15 commits into
apache:mainfrom
mbutrovich:df55

Conversation

@mbutrovich

@mbutrovich mbutrovich commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

Which issue does this PR close?

  • Closes #.

What changes are included in this PR?

Are these changes tested?

Existing tests.

AI Disclosure

Claude helped with some mechanical stuff as this was in development (bumping WIP branches and commits, API changes) but I understand and support the changes.

@mbutrovich mbutrovich changed the title deps: [DO NOT MERGE] test DataFusion 55.0 and Arrow/Parquet 59.1 deps: [DO NOT MERGE] test DataFusion 55.0 and Arrow/Parquet 59.2 Aug 13, 2026
@mbutrovich

mbutrovich commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator Author

I will get this cleaned up and ready for review today now that crates are available.

@mbutrovich mbutrovich changed the title deps: [DO NOT MERGE] test DataFusion 55.0 and Arrow/Parquet 59.2 deps: upgrade to DataFusion 55.0 and Arrow/Parquet 59.2 Aug 19, 2026
@mbutrovich
mbutrovich marked this pull request as ready for review August 19, 2026 18:08

@gabotechs gabotechs left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

👍 Everything looks good here, just the expected mechanical changes from the datfusion@55 upgrade.

@shanielh

Copy link
Copy Markdown

@mbutrovich Care to rebase this so this can be merged? :)

@dannycjones

Copy link
Copy Markdown
Contributor

@CTTY would like to see the 0.11 release branch be cut ahead of this version bump, with the reasoning being that DataFusion 54.1 can be considered stable at this point and consumers may benefit from that.
#3034 (comment)

Please can you confirm you're aligned, and we can go ahead with cutting that branch before merging this?

@dannycjones

Copy link
Copy Markdown
Contributor

That doesn't stop the rebase of course :)

@CTTY

CTTY commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

Yes, I'm leaning toward releasing 0.11 before bumping DataFusion to v55

@mbutrovich

Copy link
Copy Markdown
Collaborator Author

@CTTY would like to see the 0.11 release branch be cut ahead of this version bump, with the reasoning being that DataFusion 54.1 can be considered stable at this point and consumers may benefit from that. #3034 (comment)

Please can you confirm you're aligned, and we can go ahead with cutting that branch before merging this?

No concerns from me. Seems like 0.11 will happen pretty quickly. Note that I'm about to head on vacation until after Labor Day (US) so would need a committer to keep resolving the merge conflicts as they arise.

@dannycjones

Copy link
Copy Markdown
Contributor

Given we've now cut the 0.11.x branch, I think we're good to move forward here towards merging into main.

@kevinjqliu kevinjqliu left a comment

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.

LGTM!

@kevinjqliu

Copy link
Copy Markdown
Contributor

@dannycjones should we wait until RC passes before merging?

@dannycjones

Copy link
Copy Markdown
Contributor

@dannycjones should we wait until RC passes before merging?

I think we're OK to go ahead merging. I am planning to backport anything to branch 0.11.x if there are changes required.

@kevinjqliu
kevinjqliu merged commit 665c64e into apache:main Sep 3, 2026
22 checks passed
@kevinjqliu

Copy link
Copy Markdown
Contributor

thanks @mbutrovich and everyone for the review!

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.

6 participants