alamb commented on issue #17045: URL: https://github.com/apache/datafusion/issues/17045#issuecomment-3156649278
> Ideally to have a separate CI which triggers only if datafusion-spark crate changed. But stepping back and look at that again the submodule more reminds a separate subproject(its not a core, niche usage, separate CI, test runner). We can keep it evolving in DF repo but later it would probably make sense to move it? I think in the long term it would make sense to consider moving `datafusion-spark` out of the main datafusion repo, but I think having it in the main repo initially will reduce the friction / get more eyes on it -- 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-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
