You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by "alamb (via GitHub)" <gi...@apache.org> on 2023/12/18 13:53:46 UTC

[I] DataFusion weekly project plan (Andrew Lamb) - Dec 11, 2023 [arrow-datafusion]

alamb opened a new issue, #8577:
URL: https://github.com/apache/arrow-datafusion/issues/8577

   Follow on to [Dec 11 2023](https://github.com/apache/arrow-datafusion/issues/8490):
   
   ## Boilerplate Overview
   The idea of this ticket is make my plans for DataFusion visible, largely for my own personal organizational needs, but also to:
   1. Try some different ways to communicate / coordinate in the community 
   2. Help provide an interesting summary of what is happening in DataFusion this week
   
   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
   - [ ] Shepherd next PRs through for https://github.com/apache/arrow-datafusion/issues/8376
   - [ ]  https://github.com/apache/arrow-datafusion/issues/8491 
   - [ ] Reproduce other bugs / limitations we have hit while upgrading DataFusion in InfluxDB IOx 
   
   ## Project Queue (list of future projects)
   - [ ] https://github.com/apache/arrow-datafusion/issues/8227 (specifically, https://github.com/apache/arrow-datafusion/issues/8229 as a step towards https://github.com/apache/arrow-datafusion/issues/8078)
   
   
   ## Projects I hope to help review and coordinate
   - [ ] https://github.com/apache/arrow-datafusion/issues/8130, in support of memory explosion in HashJoin outputs: https://github.com/apache/arrow-datafusion/issues/7848 
   - [ ] Next steps towards function packages more modular (make all BuiltInScalarFunctions ScalarUDFs): https://github.com/apache/arrow-datafusion/issues/8045 with @2010YOUY01 and @edmondop . This week I hope to help get https://github.com/apache/arrow-datafusion/issues/8157 complete, and move on to https://github.com/apache/arrow-datafusion/pull/8046
   - [ ] Review any new ticket / bug reports 
   
   # Algorithm for (my) prioritizing PR reviews
   Note there are many [committers](https://arrow.apache.org/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:
   1. Bug fixes (where something is just incorrect), especially regressions (where it used to work and now does not)
   2. Improvements directly related to features needed for InfluxDB (my employer)
   3. Documentation and test improvements (I view these as very strategically important)
   4. PRs that I think are strategically important
   5. Other new features / additions to functionality
   
   The current strategically important projects in my head are:
   
   * Making function packages modular and easier to mix/match: https://github.com/apache/arrow-datafusion/issues/8045 
   * Improving performance of high cardinality aggregation (I have dreams of working on this over Christmas break)
   
   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 / 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)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org