ntjohnson1 commented on issue #1612: URL: https://github.com/apache/datafusion-python/issues/1612#issuecomment-4907966105
Option 2 seems best to me. That ballista snippet above looks really clean. There's a slight benefit to option 1 for discoverability if I could `pip install datafusion[ballista]` that makes everything feel a little more unified. However, then datafusion would want to include all downstream options. `pip install ballista` doesn't seem that bad if I know I need the distributed support. Managing the python dependencies doesn't seem too bad. I assume the pyproject for ballista and datafusion-distributed would transitively depend on datafusion-python so I don't expect there to be duplicate wheels. If someone needs the distributed option then they wait the couple of weeks after upstream lands, if not then they can get bleeding edge df-python sooner. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
