milenkovicm opened a new issue, #1245:
URL: https://github.com/apache/datafusion-ballista/issues/1245

   Following the completion of #1068, it's time to propose the next steps for 
Ballista.
   
   In the short term, I would like to focus on the following areas:
   
   - **Improving test coverage**: We continue to encounter bugs that could be 
prevented with more comprehensive unit and integration tests.
   - **Code cleanup and refactoring**: There are several areas in the codebase 
that can be simplified or refactored, which can complement the testing 
improvements.
   - **Improving shuffles module**: There are numerous open issues related to 
shuffle files, and resolving them could yield significant benefits.
   - **Job-related enhancements**: This includes improvements to job dependency 
graphs, adaptive query execution, and related functionality.
   - **Enhanced observability**: Increasing the scope of scheduler-emitted 
events, including executor-related events, will help improve visibility and 
debugging.
   - **Simplifying and improving GitHub Actions**: Streamlining our CI/CD 
processes to be more efficient and maintainable.
   
   More details will follow after further discussion with the community.
   
   Once again, thank you all for the incredible support on #1068!
   


-- 
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-unsubscr...@datafusion.apache.org.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org

Reply via email to