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

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/05/17 02:52:25 UTC

[GitHub] [arrow-datafusion] yahoNanJing commented on issue #2502: [EPIC] Move Ballista to new arrow-ballista repo

yahoNanJing commented on issue #2502:
URL: https://github.com/apache/arrow-datafusion/issues/2502#issuecomment-1128350711

   Hi @andygrove, sorry for late response. I'm not opposed to move Ballista to a new repo. However, I still have some concerns.
   1. How to manage some features which needs changes in both datafusion and ballista, like configuration refactoring?
   2. For some features, like Morsel-driven parallel execution, it leverages the **partition** for morsel splitting. However, the **partition** is also used for task splitting in Ballista. The same concept may have conflicts between datafusion and ballista, if ballista is moved out and new features are introduced to datafusion. How should we avoid that?


-- 
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

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