[
https://issues.apache.org/jira/browse/SPARK-30893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212635#comment-17212635
]
Anurag Mantripragada edited comment on SPARK-30893 at 10/12/20, 7:56 PM:
-------------------------------------------------------------------------
As mentioned above in [~cloud_fan]'s comment, should we backport the
nullability and datatype issues from this umbrella to branch-2.4 as they may
cause corruption?
CC: [~viirya], [~dongjoon]
was (Author: anuragmantri):
As mentioned here
[#https://issues.apache.org/jira/browse/SPARK-30893?focusedCommentId=17041618&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17041618],
should we backport the nullability and datatype issues from this umbrella to
branch-2.4 as they may cause corruption?
CC: [~viirya], [~dongjoon]
> Expressions should not change its data type/nullability 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
> Fix For: 3.0.0
>
>
> 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
