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/03/11 08:16:07 UTC

[GitHub] [arrow-datafusion] rdettai commented on issue #1916: Discussion: Is Ballista a standalone system or framework

rdettai commented on issue #1916:
URL: https://github.com/apache/arrow-datafusion/issues/1916#issuecomment-1064876968


   I understand that Ballista is currently heading toward being standalone system, but I am wondering that is what the ecosystem needs. 
   
   I feel that being a plugable library Datafusion is a big part of Datafusion's success. But the projects that are embedding Datafusion today as a single node compute engine, are they not going to need to be distributed tomorrow? If Ballista is really designed as a standalone system, those growing projects might use it as an example on how to distribute the Datafusion query plan, but they might not be able to reuse much code. 
   
   Also, as a standalone system, Ballista will compete with the heavy weights in the category (Spark, Presto..). That is an interesting but very ambitious goal 😄 


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