alamb commented on PR #17813: URL: https://github.com/apache/datafusion/pull/17813#issuecomment-3452668507
I have been thinking about this more -- and I am thinking more about this generic class of issues in general and I could come up with two potential workaround: 1. Add some sort of expression (`Expr::Cast`??) to cast back to the appropriate nullability, which can be substituted to ensure the nullability stays the same even though it doesn't do anything at runtime. 2. Relax the schema consistency check (e.g. it is ok if a schema goes from Nullable --> NonNullable due to optimizations as that is strictly an improvement) One of these workarounds might have less of a chance of introducing an subtle bug 🤔 -- 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]
