[GitHub] [arrow-datafusion] jorgecarleitao commented on issue #509: Prepare Ballista crates for publishing

[GitBox <gi...@apache.org>]

jorgecarleitao commented on issue #509:
URL: https://github.com/apache/arrow-datafusion/issues/509#issuecomment-856295375


   Do you have plans about what you would like Ballista to be? I.e. if we release Ballista as a binary (e.g. in artifactory, or in a docker image), we do not need DataFusion released, as we can point to a github hash. The limitation emerges when placing it in crates.io.
   
   I think that the same applies for other consumers of DataFusion. For example, the Python bindings do not require DataFusion in crate.io: we can build the wheels and ship them to pypi.
   
   Regardless, I agree with @alamb with the cadence, as some consumers may want to ship _libraries_ built on top of datafusion.
   
   @alamb , I am curious: do you need datafusion released for iox? I imagine that if you ship it as a binary or docker, you can point to the hash, right?
   
   
   


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

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