-
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
DataFusion weekly project plan (Andrew Lamb) - Feb 5, 2024 #9121
Comments
6 tasks
8 tasks
Next week: #9200 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow on to Jan 29, 2024
Note: I will be traveling this week so I will likely have less time to devote to DataFusion
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) goals for this project
1000 projects are built using DataFusion 📈
My (personal) plans for this week
datafusion-functions-array
crate) Createdatafusion-functions-array
crate and moveArrayToString
function into it #9113 and related infrastructure AddFunctionRegistry::register_udaf
andFunctionRegistry::register_udwf
#9075Project Queue (list of future projects)
Projects I plan to help actively help review / plan
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 top 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: