-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dec 3. 2024: This week in DataFusion #13630
Comments
Started a discussion / epic to track work to make upgrades easier: |
Also @Rachelint has accepted the invitation to become a committer: 🎉 : https://lists.apache.org/thread/1hznzshzd3r88dkqdhcp4s9qzgm7pzvo |
https://github.com/JanKaul/frostbow from @JanKaul looks very interesting for reading S3 tables |
Documentation / blog from @timsaucer in discord: |
Next edition: #13760 |
Introduction
This ticket is a weekly-ish summary of interesting things happening in DataFusion. Note this is not a complete list (it is what I remember / can find). Please feel free to leave comments on this ticket about things that I may have missed or you think should get wider attention by the community
Loosely inspired by https://this-week-in-rust.org/
Highlights
@findepi became a committeer 🎉
Discussions
Major Projects / Discussions under way
DataFusion Related Reading List
(looking for help updating this list):
Upcoming Releases
0.53.0
/ sqlparser_derive0.3.0
datafusion-sqlparser-rs#1517Highlights from last week(s):
(I am sorry if I missed you -- please add a note to this ticket with anything you would like to highlight)
Performance
🐛 🔨
Features
related_udf
,alternative_syntax
#13575ScalarUDFImpl::invoke_with_args
to support passing the return type created for the udf instance #13290MemoryExec
) #13540There were many small improvements / bug fixes as well.
Others
Looking to get more involved? Try code review!
DataFusion has a long history of community members contributing in all aspects of the project. Reviewing PRs is an especially great way to get introduced to the project, help the community and grow your own knowledge -- researching and understanding the code enough to review PRs also often inspires additional ideas for improvements.
We have docs about reviews. TLDR is: look for test coverage, if the change is understandable and well documented, and if the code can be improved. When you think the PR looks good to merge, try
@
mentioning one of the committers.Help wanted
Please feel leave your own comments on this ticket if you are looking for help
Community
Upcoming meetups:
Background:
Previous update:
Andrew's Focus Areas:
The text was updated successfully, but these errors were encountered: