Skip to content

Release DataFusion 49.0.0 (July 2025) #16235

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 (June, 2025) so next major release would be late June or Early July 2025

Steps:

TODOs

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 need to be fixed

Bugs that would be good to fix / investigate

Community Wishlist

Activity

  1. alamb commented on Jul 12, 2025

    @alamb
    ContributorAuthor

    I am thinking we should begin the 49.0.0 release next week. I'll publicize to the lists / etc

  2. xudong963 commented on Jul 12, 2025

    @xudong963
    Member

    @alamb Yeah, let's do it (time flies

  3. adriangb commented on Jul 13, 2025

    @adriangb
    Contributor

    We introduced new APIs in #16461 and more importantly removed the existing SchemaAdapter. I am not sure how upgrading other systems has gone but if they relied on custom SchemaAdapters they'll be broken. I think we should restore the default SchemaAdapter and make it possible to choose which path you use. To get there I think we need at least part of #15057 and to revert the change of removing SchemaAdapter in the original PR. I'm sorry if this causes a delay, I'll get to it ASAP on Tuesday.

  4. xudong963 commented on Jul 14, 2025

    @xudong963
    Member

    We introduced new APIs in #16461 and more importantly removed the existing SchemaAdapter. I am not sure how upgrading other systems has gone but if they relied on custom SchemaAdapters they'll be broken. I think we should restore the default SchemaAdapter and make it possible to choose which path you use. To get there I think we need at least part of #15057 and to revert the change of removing SchemaAdapter in the original PR. I'm sorry if this causes a delay, I'll get to it ASAP on Tuesday.

    I'm okay to wait for these changes. It's always good to not break users.

  5. alamb commented on Jul 14, 2025

    @alamb
    ContributorAuthor

    I'm okay to wait for these changes. It's always good to not break users.

    Sounds good -- I added it to the checklist on the description of this ticket

  6. adriangb commented on Jul 14, 2025

    @adriangb
    Contributor

    I'm okay to wait for these changes. It's always good to not break users.

    We're trying to minimize breakage! Thanks to you and everyone else for your your patience as we make these exciting but difficult improvements.

  7. adriangb commented on Jul 15, 2025

    @adriangb
    Contributor
  8. adriangb commented on Jul 15, 2025

    @adriangb
    Contributor

    I've opened #16791 to address backwards compatibility

  9. alamb commented on Jul 16, 2025

    @alamb
    ContributorAuthor

    I am hoping to start with some of the various release tasks tomorrow (like ensuring hte upgrade guide is in a good place) but I have been very busy with other things recently. Hopefully we can sort out #16791 soon and get the relese process started

  10. shehabgamin commented on Jul 17, 2025

    @shehabgamin
    Contributor

    Almost missed this thread. Will start testing when there is a 49 branch!

  11. alamb commented on Jul 17, 2025

    @alamb
    ContributorAuthor

    I am still behind -- i will likely start in earnest on this task tomorrow (Friday) and over the weekend and hopefully we'll be reado to cut a Release Candidate (RC) early next week

  12. 15 remaining items

  13. shehabgamin commented on Jul 23, 2025

    @shehabgamin
    Contributor

    Tested on Sail with commit afb9099. Everything looks good!

    lakehq/sail#653

  14. comphead commented on Jul 23, 2025

    @comphead
    Contributor

    Testing on Comet, seeing some test failures

    UPD: Moved to the latest DF RC branch and tracking progress apache/datafusion-comet#2040

    One weird thing is the correctness issue on the queries with first/last with ignore null flag.

    I can't find if Datafusion had changes for ignore null flag in 49 release 🤔

    UPD2: Looks like the cause is somewhere in aggregate.rs or first_last.rs

    UPD3: @alamb I think it is good to go, the reason is the ignore nulls resets the value if the grouping key lives in 2 separate parquet files. Same scenario works fine in DF, I assume some logic was moved from physical layer to logical causing Comet correctness issues when using FirstValue function. I'm still investigating it, but again the same scenario works fine in DF

    UPD4: @alamb @ozankabak @berkaysynnada @mbutrovich Filed a PR https://github.com/apache/datafusion/pull/16918/files, appreciate for thoughts

  15. xudong963 commented on Jul 24, 2025

    @xudong963
    Member

    Test MV repo with DF49, datafusion-contrib/datafusion-materialized-views#75. Looks good

  16. XiangpengHao commented on Jul 24, 2025

    @XiangpengHao
    Contributor

    I run into some compile issue in parquet viewer, still investigating...

    Update 1: I have to disable the encryption feature in Parquet to make it work: https://github.com/apache/datafusion/blob/main/Cargo.toml#L162

    It seems that it's not happy with ring, but I also saw ring already have some special handling for wasm

  17. Omega359 commented on Jul 24, 2025

    @Omega359
    Contributor

    I ran my test suite against df 49, all passed. I did have to make an update for TableParquetOptions that wasn't listed in the upgrade doc (new crypto field).

  18. alamb commented on Jul 24, 2025

    @alamb
    ContributorAuthor

    Update 1: I have to disable the encryption feature in Parquet to make it work: https://github.com/apache/datafusion/blob/main/Cargo.toml#L162

    Thanks @XiangpengHao -- do you think we should disable the crypto feature by default?

    cc @corwinjoy @adamreeve

  19. XiangpengHao commented on Jul 24, 2025

    @XiangpengHao
    Contributor

    Update 1: I have to disable the encryption feature in Parquet to make it work: https://github.com/apache/datafusion/blob/main/Cargo.toml#L162

    Thanks @XiangpengHao -- do you think we should disable the crypto feature by default?

    cc @corwinjoy @adamreeve

    @aoli-al figured out that this is an issue from my nix flake build, not a datafusion issue: XiangpengHao/parquet-viewer#50

    (but I only see this error starting df49)

    Now all tests passed with parquet viewer!

  20. adamreeve commented on Jul 24, 2025

    @adamreeve
    Contributor

    Thanks @XiangpengHao -- do you think we should disable the crypto feature by default?

    cc @corwinjoy @adamreeve

    It sounds like this is sorted but let me know if you'd like it disabled by default for the release. Corwin is on holiday but I can help with that if needed.

  21. xudong963 commented on Jul 27, 2025

    @xudong963
    Member

    The 49.0.0 is released, and I've published it to crate.io

  22. alamb commented on Jul 27, 2025

    @alamb
    ContributorAuthor

    Thank you very much @xudong963 and everyone else who helped

    I hope to publish the blog tomorrow:

  23. reopened this on Jul 27, 2025
  24. added a commit that references this issue on Jul 28, 2025
  25. alamb commented on Aug 4, 2025

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

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions