Skip to content

Release DataFusion 51.1.0 (Minor) #18843

Closed as not planned
Closed as not planned

Description

@alamb

Is your feature request related to a problem or challenge?

Follow on to

@timsaucer mentioned yesterday he was thinking about a 51.1.0 release, and there are some things that we may way to backport into the 51.0.0 line, and this ticket tracks doing so

Steps:

  • Update version and changelog
  • Test with DataFusion Python
  • Test with DataFusion Comet
  • Test with delta.rs:
  • Test vortex:
  • Test with iceberg-rust:
  • Test with LakeSail:
  • Test with parquet viewer
  • Test with datafusion-materialized-views
  • Voting Thread:
  • Publish to crates.io

Potential Content:

Bug Fixes

Minor Features:

Activity

  1. added theissue type on Nov 20, 2025
  2. Omega359 commented on Nov 20, 2025

    @Omega359
    Contributor

    arrow 57.1.0 ? Or should we wait a bit to let arrow-rs bake a bit more?

  3. alamb commented on Nov 20, 2025

    @alamb
    ContributorAuthor

    arrow 57.1.0 ? Or should we wait a bit to let arrow-rs bake a bit more?

    In theory, we shouldn't have to do anything to DataFusion 51.0.0 to be able to use arrow 57.1.0 as it is semver compatible (and @etseidl and I are madly testing to make sure this is true):

    I do think several tests will need to be updated to get them to pass with arrow 57.1.0 (see #18820) but I am not sure if we should do that or not

  4. tschwarzinger commented on Dec 1, 2025

    @tschwarzinger
    Contributor

    If we're creating a 51.1.0 version I can create a PR for back porting #18903 .

  5. alamb commented on Dec 1, 2025

    @alamb
    ContributorAuthor

    If we're creating a 51.1.0 version I can create a PR for back porting #18903 .

    I think it is quite likely we'll make a 51.1.0 -- I just don't know when we will release it.

    @tobixdev it would be great if you made the backport PR and we'll get it merged and be ready to go

  6. vustef commented on Dec 1, 2025

    @vustef

    I am not sure if we should do that or not

    If it helps, +1 for getting this release upgraded to arrow 57.1. Just a preference, of course happy to wait for 52.0.

  7. timsaucer commented on Dec 7, 2025

    @timsaucer
    Member

    @xudong963 @alamb Thanks for the merges in - now #18657 is in the green!

  8. alamb commented on Dec 8, 2025

    @alamb
    ContributorAuthor

    Are we ready to make a RC?

  9. timsaucer commented on Dec 9, 2025

    @timsaucer
    Member

    🤦 The correct PR for the catalog provider list is: #18912 (not #18657 I linked above)

  10. alamb commented on Jan 13, 2026

    @alamb
    ContributorAuthor

    Given we have now released 52.0.0 I think it is unlikely we will do a 51 patch release unless there is significant demand

  11. reopened this on Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions