-
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) - Dec 18, 2023 #8577
Comments
8 tasks
alamb
changed the title
DataFusion weekly project plan (Andrew Lamb) - Dec 11, 2023
DataFusion weekly project plan (Andrew Lamb) - Dec 18, 2023
Dec 18, 2023
(moved down) |
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow on to Dec 11 2023:
Boilerplate Overview
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 if anyone else who has plans like this for DataFusion could try to make them visible somehow as well
My (personal) plans for this week
<col> = 'const'
inPruningPredicate
#8376Project Queue (list of future projects)
Projects I hope to help review and coordinate
JoinHashMap
forHashJoin
#8130, in support of memory explosion in HashJoin outputs:HashJoinStream
memory tracking insufficient #7848BuiltInScalarFunction
) #8045 with @2010YOUY01 and @edmondop . This week I hope to help get SupportExpr
creation forScalarUDF
: Resolve function calls by name during planning #8157 complete, and move on to RFC: Demonstrate what a function package might look like -- encoding expressions #8046Algorithm for (my) prioritizing PR reviews
Note there are many committers who can and review and merge PRs, so this is not the priorities of the project as a whole, just the approximate algorithm I am using
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 / etc.
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: