Repository navigation
Release DataFusion 51.0.0 (Nov 2025) #17558
Description
Activity
Should the title of this issue say 51.0.0 instead of 50.0.0?
- changed the title
[-]Release DataFusion `50.0.0` (Nov 2025)[/-][+]Release DataFusion `51.0.0` (Nov 2025)[/+]on Sep 15, 2025 Should the title of this issue say 51.0.0 instead of 50.0.0?
yes, thank you, i changed it.
Reacted by Andrew LambI removed #16842 from "Changes to add to upgrade guide". I think it was completed in 50.0.0. If not, let's add it back.
Reacted by Andrew LambI think we could start working on the release next week?
Reacted by Andrew LambIf we could get the following arrow fix merged and released as a patch and upgrade to that patch before the upcoming release it would be sweet:
If we could get the following arrow fix merged and released as a patch and upgrade to that patch before the upcoming release it would be sweet:
I think that one will be released in arrow 57.1.0 (a minor update that won't require a datafusion upgrade).
So once we have released datafusion 51 we'll be able to do a minor update to arrow 57.1.0
(in other words, I don't think the release timeline of DataFusion will impact the flow of that PR)
Reacted by Raz LuvatonFYI, I plan to cut the 51.0.0 in the next two days. Do we have some high-priority PRs waiting for review?
@Omega359 do we have additional work needed for the default timezone fixes?
- E.g. follow ups from Change default
time_zonetoNone(was"+00:00") #18359
- E.g. follow ups from Change default
@alamb - the outstanding ones I've got on my radar are
- Respect execution timezone in
to_timestampand related functions #18025 - feat: add RESET statement for configuration variabless #18408 (new feature, not in critical path)
- Feat: Make extract SQL expression timezone aware #18417 (been broken for quite a while now)
I'd like to get the first one in for 51.0.0. The other two while nice to have I do not see as critical
- Respect execution timezone in
I'd like to get the first one in for 51.0.0. The other two while nice to have I do not see as critical
Thanks @Omega359 -- added it to the list above
I also think we need to fix this regression:
We're working on testing Sail on our end.
37 remaining items
It seems like all PRs are added to branch-51, cc @comphead @timsaucer
Time to start the RC2
Reacted by Andrew Lamb and Oleks VTime to start the RC2
I think we still need to update changelog before releasing, will do later
Time to start the RC2
I think we still need to update changelog before releasing, will do later
Could anyone help do this? My network has been bad for a long time:
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Request GET /repos/apache/datafusion/commits/e14322da196a75bea2de2be560b93ea7c8e83d11/pulls failed with 403: rate limit exceeded Setting next backoff to 3503.394145sCould anyone help do this? My network has been bad for a long time:
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Request GET /repos/apache/datafusion/commits/e14322da196a75bea2de2be560b93ea7c8e83d11/pulls failed with 403: rate limit exceeded Setting next backoff to 3503.394145sDone!
BTW this happens to me when I don't use my github token (the rate limit is apparently much stricter). I made a PR to add a note to the docs:
- added a commit that references this issue
on Nov 14, 2025 - added a commit that references this issue
on Nov 14, 2025 - added a commit that references this issue
on Nov 15, 2025 @alamb thank you, just started the vote process https://lists.apache.org/thread/k2ygp0c1rp56ww44lljf0yg6qf60q5f7
Reacted by Andrew Lamb and Oleks V- added a commit that references this issue
on Nov 15, 2025 Done
Reacted by Andrew Lamb and Matt ButrovichThank you @xudong963 -- amazing as alwasy
Reacted by xudong.w and Matt Butrovich
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 #16799 (Sep, 2025) so next major release would be approximately late Nov 2025
Steps:
branch-51branch: https://github.com/apache/datafusion/tree/branch-5152.0.0(Dec 2025 / Jan 2026) #1856651.0.0release #18548TODOs
Prior release tickets:
50.0.0(Aug/Sep 2025) #16799Related
Features to mention in the blog (if they make it)
WHERE,ORDER BY,LIMIT,SELECT,EXTENDpipe operators #17278 (comment)metadata_size_hint) #18118datafusion-cli] Add a way to see what object store requests are made #17207Issuses needed
Bugs that should be fixed
DATE_TRUNCexpression regression for values before epoch #18334common_sub_expression_eliminatefails in a window function #17852current_date() = cast(now() as date);#18062Community Wishlist
DataFrameWriteOptions::with_single_file_outputproduces a directory #13323to_timestampand related functions #18025