Skip to content

Release DataFusion 48.0.0 (June 2025) #15771

Closed

Description

@alamb

Is your feature request related to a problem or challenge?

Tracking ticket for next release, also a place to track desired inclusions

Previous release will be https://crates.io/crates/datafusion/47.0.0 (April, 2025) so next major release would be late May or Early June 2025

Steps:

Prior release tickets:

Changes to add to upgrade guide

These PRs made changes that deserve a mention in the upgrade guide

Features to mention in the blog (if they make it)

Bugs that would be good to fix

Community Wishlist

Activity

  1. xudong963 commented on Apr 21, 2025

    @xudong963
    Member
  2. andygrove commented on May 24, 2025

    @andygrove
    Member

    Since updating Comet to use latest DataFusion (pinned dependency), we have been seeing regular but intermittent CI failures that we are still trying to debug.

    It may or may not be related to changes in DataFusion since 47.0.0 .. we do not know the root cause yet, but mentioning this here just in case others are seeing similar issues or have any thoughts on what may be happening.

    apache/datafusion-comet#1786

  3. alamb commented on May 25, 2025

    @alamb
    ContributorAuthor

    I am not sure if it is related, but we have also seen some intermittent failures in DataFusion CI

  4. xudong963 commented on May 28, 2025

    @xudong963
    Member

    @alamb, how about starting test next week?

  5. alamb commented on May 28, 2025

    @alamb
    ContributorAuthor

    @alamb, how about starting test next week?

    I think that would be a great idea. Thanks @xudong963

  6. andygrove commented on May 29, 2025

    @andygrove
    Member

    Since updating Comet to use latest DataFusion (pinned dependency), we have been seeing regular but intermittent CI failures that we are still trying to debug.

    This issue was not related to upgrading to use the latest DataFusion.

  7. xudong963 commented on Jun 3, 2025

    @xudong963
    Member

    I plan to update version and changelog today and then test with MV tomorrow.

    I hope we can start the vote process on Friday, and release early next week.

  8. shehabgamin commented on Jun 3, 2025

    @shehabgamin
    Contributor

    I plan to test over the next couple of days as well.

  9. alamb commented on Jun 3, 2025

    @alamb
    ContributorAuthor

    I hope to begin working on the delta-rs upgrade tomorrow as well

  10. xudong963 commented on Jun 4, 2025

    @xudong963
    Member
  11. andygrove commented on Jun 4, 2025

    @andygrove
    Member

    48.0.0 rc1 is ready: https://github.com/apache/datafusion/tree/48.0.0-rc1

    Thanks @xudong963. I'll start testing this with Comet.

    I don't seem to have received an email about the start of the vote for this release candidate.

  12. xudong963 commented on Jun 4, 2025

    @xudong963
    Member

    I don't seem to have received an email about the start of the vote for this release candidate.

    I was thinking of starting the vote after testing, maybe Friday. WDYT?

  13. 26 remaining items

  14. xudong963 commented on Jun 6, 2025

    @xudong963
    Member
  15. timsaucer commented on Jun 6, 2025

    @timsaucer
    Member

    The one I was hoping to get in but didn’t make it before this vote started was #16170

    This was the last of the breaking metadata changes. Without it we lose metadata when we operate on literals during optimization.

  16. XiangpengHao commented on Jun 6, 2025

    @XiangpengHao
    Contributor

    No issue found from Parquet Viewer and LiquidCache!

  17. andygrove commented on Jun 6, 2025

    @andygrove
    Member

    Upgrading Comet to use rc2 causes tests to fail with a attempt to subtract with overflow panic. This did not happen with rc1. I have not debugged this yet to find the root cause.

    Tracking issue: #16308

  18. andygrove commented on Jun 6, 2025

    @andygrove
    Member

    Upgrading Comet to use rc2 causes tests to fail with a attempt to subtract with overflow panic. This did not happen with rc1. I have not debugged this yet to find the root cause.

    Tracking issue: #16308

    I did confirm that reverting #16234 fixes the issue

  19. alamb commented on Jun 6, 2025

    @alamb
    ContributorAuthor

    Update:

    So I think we need to make an rc3. Thank you for bearing with us @xudong963

    I also plan to look at PR that @timsaucer and @paleolimbot suggest, but given that we are in the final testing phase unless it is without risk I would be inclined to postpone that until 49.0.0 (sorry 😭 )

  20. alamb commented on Jun 6, 2025

    @alamb
    ContributorAuthor

    BTW I think we should cut any release candidate off the release-48 branch and main is now open for 49.0.0 features

  21. andygrove commented on Jun 6, 2025

    @andygrove
    Member

    Here is the cherry-pick PR to backport #16170 into branch-48. Once this is merged, we can cut rc3.

    #16315

  22. xudong963 commented on Jun 7, 2025

    @xudong963
    Member

    I'm cooking rc3!

  23. xudong963 commented on Jun 7, 2025

    @xudong963
    Member
  24. alamb commented on Jun 11, 2025

    @alamb
    ContributorAuthor

    We have released to crates.io so I think we are all good with this release

  25. blaginin commented on Jun 19, 2025

    @blaginin
    Member

    Do you think we need to do 48.0.1 to include fix for #16444?

  26. alamb commented on Jun 20, 2025

    @alamb
    ContributorAuthor

    Do you think we need to do 48.0.1 to include fix for #16444?

    I think we can argue if that was a regression or not (it was a change of a default setting, though we are about to change it again in 49....)

    I volunteer to do the release candidate / voting thing if others agree we should do it

    @blaginin maybe you can make a new ticket to discuss the possibility of 48.0.1 explicitly?

  27. added a commit that references this issue on Jul 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions