-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
DataFusion weekly project plan (Andrew Lamb) - Jan 22, 2024 #8933
Comments
Can we also add #8894 to the queue please? |
This is my review queue -- it would be great if other contributors can help review PRs. I am unlikely to be able to review all of these DataFusion
Comet: Arrow Sqlparser Watching |
Sounds good, thanks! |
Next week: #9030 |
Follow on to Jan 15, 2024
Boilerplate Introduction
The idea of this ticket is make my plans for DataFusion visible, largely for my own personal organizational needs, but also to:
It would be great for other contributors to DataFusion who plan non trivial work could try to make them visible somehow as well 🙏 (feel free to copy / modify the format)
My (personal) plans for this week
HashJoinStream
#8020 from @korowaCOUNT( DISTINCT ...)
for strings (up to 9x faster) #8849 with @jayzhan211datafusion-functions
crate, extract encode and decode to #8705 reviewed, address comments, file follow on ticketsProject Queue (list of future projects)
Projects I am prioritizing reviewing / helping
BuiltInScalarFunction
) #8045 (thank you @guojidan)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:
The current strategically important projects in my head are:
BuiltInScalarFunction
) #8045Thus, 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, 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)
The text was updated successfully, but these errors were encountered: