andygrove commented on issue #872: URL: https://github.com/apache/datafusion-python/issues/872#issuecomment-2358548162
I've been thinking some more about where this code should live. I am now leaning towards putting the code into a new standalone `datafusion-ray` repository. My reasoning for this: - We have only just gotten to the point where were have multiple people regularly maintaining the `datafusion-python` project and I don't think that we should put an additional burden on these maintainers - As @ozankabak mentioned, perhaps it is better to keep `datafusion-python` as a single node thing focusing on excellent bindings to core and then have `datafusion-ray` depend on `datafusion-python`. This will be an excellent way to ensure that `datafusion-python` has sufficient extension points to enable distributed use cases. - If the project fails to gain traction, then we haven't polluted the `datafusion-python` repo with unmaintained code -- 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]
