[ https://issues.apache.org/jira/browse/SPARK-30893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041903#comment-17041903 ]
Takeshi Yamamuro commented on SPARK-30893: ------------------------------------------ Ah, I see. As for the second case, I think we need to share the idea in the dev-mailing list and collect more info. to minimize the impact on applications. As viirya said above, the consistent behaviour is important, so we need to carefully check behaviours config-by-config... > Expressions should not change its data type/behavior after it's created > ----------------------------------------------------------------------- > > Key: SPARK-30893 > URL: https://issues.apache.org/jira/browse/SPARK-30893 > Project: Spark > Issue Type: Bug > Components: SQL > Affects Versions: 3.0.0 > Reporter: Wenchen Fan > Priority: Critical > > This is a problem because the configuration can change between different > phases of planning, and this can silently break a query plan which can lead > to crashes or data corruption, if data type/nullability gets changed. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org