Skip to content

Release DataFusion 48.0.1 #16486

Description

@blaginin

Previous release: #15771

Creating this issue to discuss if we want to do a patch release to

Activity

  1. blaginin commented on Jun 20, 2025

    @blaginin
    MemberAuthor

    posting here @alamb's comment for transparency:

    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....)

    That sounds like a valid point to me. Nothing has seriously broken, and if it's too slow, users can tweak the config.

    Not sure if we want to fix the topk pushdown issues? Given that our own test suite is failing, can we sometimes produce incorrect results for users?

  2. timsaucer commented on Jun 20, 2025

    @timsaucer
    Member

    If we do a patch release I would like to get in this bugfix that I found today: #16480

  3. alamb commented on Jun 20, 2025

    @alamb
    Contributor

    I think the topK stuff was not included in 48.0.0 so there is no need to backport any fixes

    I volunteer to run the release process.

    In terms of fixing the regression in clickbench performance (which is due to statistics not being gathered by default for dataframes) with I think we have two options

  4. alamb commented on Jul 2, 2025

    @alamb
    Contributor

    I think this bug is enough to make me want to do s 48.0.1 release

    I will begin work on such a release later today

  5. changed the title [-][Potentially] Release DataFusion `48.0.1`[/-] [+]Release DataFusion `48.0.1`[/+] on Jul 2, 2025
  6. self-assigned this
    on Jul 2, 2025
  7. alamb commented on Jul 2, 2025

    @alamb
    Contributor

    The process will be:

    1. We will create backport PRs for fixes, following the instructions here https://github.com/apache/datafusion/blob/main/dev/release/README.md#how-to-backport-add-changes-to-branch--branch
    2. I'll plan to make an Release Candidate from branch-48 in the next day or two

    I will handle backporting

    If anyone else has fixes or changes they would like to include in 48.0.1, please create a backport PR (targeting the branch-48 branch)

  8. alamb commented on Jul 2, 2025

    @alamb
    Contributor

    @xudong963 do you have additional suggestions for issues that should be backported?

  9. alamb commented on Jul 2, 2025

    @alamb
    Contributor

    I have made some backport PRs:

    I'll wait another day or two see if there is any more content needed for this release

  10. blaginin commented on Jul 2, 2025

    @blaginin
    MemberAuthor

    Also opened #16659 to discuss

  11. alamb commented on Jul 4, 2025

    @alamb
    Contributor

    Ok, I have backported the three identified issues and I will now create a release candidate

  12. alamb commented on Jul 5, 2025

    @alamb
    Contributor
  13. xudong963 commented on Jul 6, 2025

    @xudong963
    Member

    @xudong963 do you have additional suggestions for issues that should be backported?

    Sorry, just come back, lgtm.

  14. alamb commented on Jul 7, 2025

    @alamb
    Contributor

    released to crates.io and all is good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

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