pepijnve commented on issue #17801: URL: https://github.com/apache/datafusion/issues/17801#issuecomment-3343252397
> 1. Why is the planner benchmark (implicitly calling `optimize` twice) > 2. What to do about the nullability change I'm preparing a draft PR with a spot fix. For 1. I've changed the test case so that it doesn't call optimize prior to creating a physical plan For 2. I've added rudimentary nullability analysis to logical and physical case. This eliminates the nullability change. It's not a very elegant fix, but perhaps good enough for now? -- 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]
