[
https://issues.apache.org/jira/browse/SPARK-30893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041576#comment-17041576
]
Takeshi Yamamuro commented on SPARK-30893:
------------------------------------------
Yea, I've already seen someone opening PRs for this issue and the idea looks
pretty reasonable to me..... we shouldn't change results in that case because
the change looks error-prone in applications. But, I think this change has a
big impact on the existing Spark users. We can simply change the behaviour even
on major release, e.g., 3.0?
> 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.
--
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
