rkrishn7 commented on issue #14394: URL: https://github.com/apache/datafusion/issues/14394#issuecomment-2644048701
@jonahgao Thank you for calling this out. I think you're right! In fact, I think we could say more generally, this issue arises when the schema of the source of an `INSERT` statement contain fields that differ from the table schema in terms of nullability. I think a better approach may be to map the schema of the source plan to a new schema that demonstrates parity in field nullability with the table schema. We could do this directly when planning the insert, after constructing the source `LogicalPlan`. In `insert_to_plan`. I opened a new issue for this here - https://github.com/apache/datafusion/issues/14550 Would love a sanity check from you to verify the above makes sense! -- 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
