Repository navigation
Release DataFusion 56.0.0 (Oct/Nov 2026) #24461
Description
Is your feature request related to a problem or challenge?
Previous release is #22393 (Jul / Aug 2026) so next major release would be approximately Sep / Oct 2026.
Steps:
- Create a
branch-56branch - Update version and changelog
- Test with DataFusion Python
- Test with DataFusion Comet - deps: upgrade to DataFusion 56.0.0 datafusion-comet#7249
- Test with DataFusion Ballista
- 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
- Create ticket for next release: Release DataFusion
56.1.0(minor/patch) Release (Nov 2026) #24463 / Release DataFusion57.0.0(Dec 2026 / Jan 2027) #25901 - Create blog post
Features to mention in the blog (if they make it)
-
ASOFjoins from @Xuanwo : ASOF join support / Specialize Range Joins #318 - Enable TopK per Partition (
datafusion.optimizer.enable_window_topn) by default #24608 - Push down topk through join #21621
- Add write support to Avro format #24925 from @pepijnve
- Add support for SQL based registration of external catalogs #25111 from @pepijnve
Bugs/issues that should be fixed
- Side effects from
serde_json/preserve_orderfeature impact user applications #25883 @adriangb - [dbolympics] fix: cast outer projection expr to declared field type in SingleDistinctToGroupBy #26211 from @jayzhan211
- Rename
LogicalPlan::DescribeTabletoLogicalPlan::Showmove statement implementations out ofsqlmodule #26057 from @pepijnve (to reduce API churn) - refactor: register proto decoders with
T::register_protoinstead of a free function #26565 from @adriangb (so it is not a breaking change later) - feat: allow extension DataSources to decode via a per-type registry #26555 from @gabotechs (so the proto type-registry refactor from feat: allow extension
ExecutionPlans to decode via a per-type registry instead ofPhysicalExtensionCodec#24631 / feat: allow extensionPhysicalExprs to decode via a per-type registry #24628 does not ship in an intermediate state) -
DISTINCT ONwith nested payloads can fail memory reservation after spilling #26744 from @shehabgamin - Multi-key null-aware join silently defaults to one NOT IN value key #26569 from @jayzhan211
- Regression:
ORDER BY col, (scalar subquery) LIMITover aRIGHT JOINfails inSanityCheckPlan#26572
Community Wishlist
- Further improve performance of IN list evaluation #19241
- [EPIC] A Collection of Wrong Results Bugs - Q4 2026 #26672 from @alamb
- datafusion-physical-expr: add
DynamicFilterPhysicalExpr::update_from(Self)method #26534 @jayshrivastava - feat: store start/end bounds in
Partitioning::Range#26593 @jayshrivastava
Reacted by Adam Gutglick and Jens Holdgaard Pedersen
Metadata
Metadata
Assignees
Labels
No labels
Activity
[-]Release DataFusion `56.0.0` (Sep / Oct 2026)[/-][+]Release DataFusion `56.0.0` (Oct 2026)[/+]xudong963 commentedon Aug 26, 2026
I can help with this release!
Xuanwo commentedon Sep 9, 2026
Really hope #318 can deliever in v56.0, let's rock!
alamb commentedon Sep 9, 2026
318 -- perhaps the lowest issue number left open that tracks something useful. A long standing request
Xuanwo commentedon Sep 14, 2026
One more question: what testing needs to be done for releases? Perhaps we could also include
lance. I'm willing to take on all the related work.alamb commentedon Sep 15, 2026
Thanks @Xuanwo -- I think what we typically do is to use the release ticket to coordinate testing with downstream crates that wish to help as we get close to making a release candidate. So for example, @AdamGS often tests with Vortex as part of that process.
Here is an example in the 55 release ticket where we were disucssing it
55.0.0(Jul / Aug 2026) #22393 (comment)alamb commentedon Sep 15, 2026
Since this release will have an update to arrow/parquet to version 60, perhaps this would be a good candidate to try out "LTS" / Long term support: #16622
kumarUjjawal commentedon Sep 15, 2026
Datafusion 56.0 will be in a good stable condition for downstream consumers and should be good starting point for new projects. So LTS makes sense.
alamb commentedon Sep 16, 2026
FYI @hareshkh who was asking about a more stable branch / backports in the call today
[-]Release DataFusion `56.0.0` (Oct 2026)[/-][+]Release DataFusion `56.0.0` (Oct/Nov 2026)[/+]alamb commentedon Sep 28, 2026
Adjusting date from Oct --> Oct/Nov as we are also working on a 55.2:
55.2.0(patch) Release (Oct 2026) #25758adriangb commentedon Sep 30, 2026
I would like to land a fix for #25883 before next release
[branch-55] fix: frame IPC messages when reading spill files so batch…
jayshrivastava commentedon Oct 22, 2026
👋🏽 Flagging a couple changes I would like to see in df56 :)
DynamicFilterPhysicalExpr::update_from(Self)method #26534Partitioning::Range#2659313 remaining items
gabotechs commentedon Oct 27, 2026
Would be nice to get this on landed as well cc @adriangb:
As other wise the proto type-registry refactor will be shipped in an intermediate state (#24631 and #24628 by @adriangb).
alamb commentedon Oct 28, 2026
Proposal to slow down features for a while to stabilize for this release
test: pin parquet `created_by` in tests so expected output is indepen…
xudong963 commentedon Nov 2, 2026
Plan to do the release tomorrow. Please let me know if you have something in mind!
jayshrivastava commentedon Nov 2, 2026
If anyone has time, I'm still looking for reviews on #26593. I'm hoping to get this in df56 to support range-aware shuffling in datafusion-distributed :)
cc @xudong963
alamb commentedon Nov 2, 2026
I would also really like to get some fixes for the wrong results in
If possible, @xudong963 perhaps you can make the branch tomorrow but wait a few more days for to make an RC? That way we can get any final fixes, etc in but not hold up main
mbutrovich commentedon Nov 2, 2026
Taking a look today.
Set version on main to `56.0.0-dev`, document release versioning sche…
xudong963 commentedon Nov 3, 2026
Sure, I'll do that
xudong963 commentedon Nov 3, 2026
FYI, just cut the branch-56 https://github.com/apache/datafusion/tree/branch-56
And two follow-up PRs:
a) Set version on main to 57.0.0-dev: #27031
b) Add branch-56 protection: #27030
I'll wait for a few days to do the final release, in the meantime, we can port PRs to the branch-56.
brancz commentedon Nov 3, 2026
Would highly appreciate if we could get these two in for 56, both of which are crucial for us to enable disk spilling:
I think they should both be relatively straight forward to review and uncontroversial since no APIs are touched.
AdamGS commentedon Nov 3, 2026
@brancz I'll try and take a look today, might require backporting
brancz commentedon Nov 3, 2026
Let me know if there is anything I can do @AdamGS!
Set version on main to `57.0.0-dev` (apache#27031)
joseph-isaacs commentedon Nov 3, 2026
Here is the vortex rc pr: vortex-data/vortex#10309