andygrove commented on issue #2187: URL: https://github.com/apache/datafusion-comet/issues/2187#issuecomment-3211342413
I'd like to bring @mbutrovich into the discussion since we have been discussing where optimization rules should live. I think we are leaning towards keeping the scala plan representation as close to the Spark plan as possible and handle adding additional nodes on the native side. I do think we should continue exploring adding coalesce execs similar to how DataFusion does this in a physical optimizer rule. -- 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
