alamb commented on issue #1273: URL: https://github.com/apache/arrow-datafusion/issues/1273#issuecomment-963577840
TDLR is I think Ballista hold much promise of value, but it needs a champion to push it forward; If it turns into a stagnated / vestigial project it will just be overhead and leaves a great amount of potential value unlocked. > I am unable to contribute to Ballista myself at the moment and I don't think the project has reached sufficient momentum for others to be motivated to continue driving it forward, although I haven't been following closely and may have missed some discussions. I think this is what Ballista is really missing -- a champion / cheerleader to drive its development forward. It seems to have mostly stalled since being brought into this repo. > The benefits of having Ballista in the codebase are, in my opinion: > It helps keep physical plans serializable Yes, I agree this is valuable, (and is actually the largest source of overhead in my opinion) -- any change to `LogicalPlan` or `Expr` requires being able to update the protobuf serialization / deserialization code. I think @rdettai is out for the next few days / weeks but some things he said recently made me think he was planning to focus more on Ballista (perhaps our champion emerges...) At some point IOx (my company's project) will care about distributed query execution, and at that point we may bring more energy to bear on Ballista, but realistically that is not likely to happen for 6+ more months. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
