[
https://issues.apache.org/jira/browse/SPARK-30893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043195#comment-17043195
]
Hyukjin Kwon commented on SPARK-30893:
--------------------------------------
I am sure there are already multiple inconsistent instances out there. Probably
some configurations would need more destructive fixes. Are they worthwhile? I
am not sure.
It seems to me a bit unlikely users set a different configurations that change
behaviours between queries.
For these data type related instances, they look easy to fix so probably fine
for now. I am not so supportive of fixing other instances.
> 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
