Description
Follow on to #11474
My (personal) North ⭐ : 1000 projects are built using DataFusion 📈
It would be great for other contributors to DataFusion to to make them visible somehow as well 🙏 (feel free to copy / modify the format of this ticket)
Major Discussions (I would encourage to take a look)
- roadmap: 2024 Q3-Q4 Roadmap? #11442
- Logical Types: [Proposal] Decouple logical from physical types #11513 from @notfilippo
- Split out catalog (and change
TableProvider): Extract catalog API to separate crate, changeTableProvider::scanto take a trait rather thanSessionState#11516 from @findepi - Add
ParquetMetadataWriterallow ad-hoc encoding ofParquetMetadataarrow-rs#6000: Apis for working with parquet metadata from @adriangb
External news
- Meetup in Hangzhou, China 🎉 DISCUSSION: DataFusion Meetup in China #10341 (comment) (thanks @waynexia , @tisonkun and @liukun4515
Upcoming Meetups
- DataFusion Belgrade Meetup 2024/09/27 #11431
- New York, NY, USA DataFusion Meetup: Tuesday Sep 17th 2024, 5:30PM - 8:30PM Manhattan #11213
Feature Highlights
- Completed [EPIC] Continued correct and improved extracting Parquet statistics into ArrayRefs #10922 @efredine has Add parquet
StatisticsConverterfor arrow reader arrow-rs#6046 🎉
- Completed SQL planner extension API Discussion: make it easier for specify SQL --> function translation #10534 with @jayzhan211 and @samuelcolvin, @xinlifoobar, @dharanad)
My (personal) plans for this week
- Finish Blog: Blog post with DataFusion Jan - June 2024 #9602,
- Work down the review backlogs
Projects I plan to help actively help review / push forward
- Various upstream parquet metadata changes: Add
ParquetMetadataWriterallow ad-hoc encoding ofParquetMetadataarrow-rs#6000, Do not writeColumnIndexfor null columns when not writing page statistics arrow-rs#6011, Add size statistics toParquetMetaDataintroduced in PARQUET-2261 arrow-rs#5486, with @etseidl and @adriangb - Help push user defined aggregates over the line ([Epic] Unify
AggregateFunctionInterface (remove built in list ofAggregateFunctions), improve the system #8708) - thanks to @Rachelint and @jcsherin) - [EPIC] Implement
StringViewArrayandBinaryViewArrayarrow-rs#5374 and [Epic] Implement support forStringViewin DataFusion #10918 with @XiangpengHao @a10y and others
Algorithm for (my) prioritizing PR reviews
Note there are many committers who can and do review and merge PRs, so this is not the priorities of the project as a whole, just the approximate algorithm I use to prioritize my own time.
Priority:
- Bug fixes (where something is just incorrect), especially regressions (where it used to work and now does not)
- Improvements directly related to features needed for InfluxDB (my employer)
- Documentation and test improvements (I view these as very strategically important)
- PRs for other features I think are strategically important (See below)
- Other new features / additions to functionality (note this is the lowest on purpose)
The top strategically important projects in my head are:
- Improved performance (with benchmarks -- this is higher in my mind now)
- Anything that makes it easier to use DataFusion as a user (docs, examples, better APIs, etc), including Getting started guide for new users (who want to use DataFusion in their project)
- Anything that improves DataFusion's quality such as bug fixes, and improved / expanded tests, etc
Thus, if you are interested in contributing to DataFusion and are interested in a fast turn around time I would recommend looking into bug fixes / test improvements / documentation or the projects named above.
If you propose adding new functionality, especially if the PR is large/complex and not connected to a wider need, the review cycle will likely be longer. You can make it a shorter cycle by looking at the comments on other recent PRs and following the same model (e.g. ensure there are tests in sqllogictest for example, the CI passes, includes documentation, etc)
Background
The idea of this ticket is make my plans for DataFusion visible, largely for my own personal organizational needs, but also to:
- Communicate / coordinate in the community
- Help provide an interesting summary of what is happening in DataFusion this week (both for my future self and others)