Release DataFusion `50.1.0` (minor)

[alamb]

Is your feature request related to a problem or challenge?

• Follow on to Release DataFusion 50.0.0 (Aug/Sep 2025) #16799

There are some things that we may way to backport into the 50.0.0 line, and this ticket tracks doing so
Steps:

• Update version and changelog: [branch-50] Prepare for 50.1.0 release #17748
• 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: https://lists.apache.org/thread/jch5tfvc9yzf7zrro61hcqbclqmsr4xr
• Publish to crates.io
• Create ticket for next release:

Potential Content:

Bug Fixes

• Exponential planning time when window function is partitioned by multiple columns #17401 / Prevent exponential planning time for Window functions #17563 / Prevent exponential planning time for Window functions - v2 #17684
• fix: ignore non-existent columns when adding filter equivalence info in FileScanConfig #17546
• fix: Ensure the CachedParquetFileReader respects the metadata prefetch hint #17302
• Partial AggregateMode will generate duplicate field names which will fail DFSchema construct #17662
• [branch-50] Partial AggregateMode will generate duplicate field names which will fail DFSchema construct to branch-50 #17717

Minor Features:

• feat: expose udafs and udwfs methods on FunctionRegistry #17650

[alamb]

I can help run this release process unless someone else wants to

[milenkovicm]

I'm a bit late on datafusion release party, I wonder if 50.0.1 could hold #17596 which is a backward incompatible change

Edit: incompatible change, does not make sense to go to patch release, sorry for the noise.

[rkrishn7]

@alamb #17600 to backport 17546

[shehabgamin]

#17613

[milenkovicm]

Due to #17596 ballista would not be able to support datafusion 50 I can provide a workaround but would mean we would need to release 50.1.0 could we consider 50.1 release instead?

Change would be adding two new methods to FunctionRegistry

[alamb]

Change would be adding two new methods to FunctionRegistry

I think adding two new methods and releasing 50.1.0 sounds good to me

@findepi and I are still going back and forth a bit on the solution to

• Prevent exponential planning time for Window functions #17563

[milenkovicm]

thanks @alamb, I'll try to make a PR tonight