[DISCUSSION] 2025 Q1-Q2 Roadmap

We have had past roadmap discussions:

Let's use this ticket to coordinate / discuss our priorities for the next few months

@XiangpengHao

I personally plan to focus on

🚀 performance: Help complete the advanced parquet predicate pushdown with @XiangpengHao Enable parquet filter pushdown (filter_pushdown) by default #3463
🔨 Improve build time: Build time regression #14256 (thanks to @logan-keede who is helping break)
📖 : trying to keep the documentation high quality [Epic] Better / Improved Documentation, Tutorials and Examples #7013 (thanks @@ugoa for the recent help ❤ )
📈 : keep doing pre-release testing [DISCUSS] More extensive pre-release testing #13661
Easier query remote data systems [DISCUSSION] Make it easier and faster to query remote files (S3, iceberg, etc) #13456
Helping Comet and other systems aiming to provide spark compatible runtimes: [DISCUSSION] Add separate crate to cover spark builtin functions #5600. I think this is a common and recurring use case

Stuff I am personally unlikely to spend much time on (aka looking for help)

Adding new functions to the core (I understand the value, but they can be added outside and just adding more functions to the core adds maintenance burden on maintainers). So I am hesitant to accept new functions without additional new maintenance bandwidth
Revamping coercion (as much as it needs it). I think it is in good hands with @jayzhan211 and @shehabgamin, eg. Signature::Coercible with user defined implicit casting #14440

My personal list

I'll try to chase

I filed a ticket to discuss the next few months:

Navigation Menu