You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2022/02/28 10:23:00 UTC
[jira] [Commented] (SPARK-38347) Nullability propagation in transformUpWithNewOutput
[ https://issues.apache.org/jira/browse/SPARK-38347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498815#comment-17498815 ]
Apache Spark commented on SPARK-38347:
--------------------------------------
User 'sigmod' has created a pull request for this issue:
https://github.com/apache/spark/pull/35677
> Nullability propagation in transformUpWithNewOutput
> ---------------------------------------------------
>
> Key: SPARK-38347
> URL: https://issues.apache.org/jira/browse/SPARK-38347
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.2.0
> Reporter: Yingyi Bu
> Priority: Major
>
> The nullability of a replaced attribute should be `a.nullable` instead of `b.nullable`:
> https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/QueryPlan.scala#L357
> The scenario is a left outer join where the RHS attributes are replaced bottom up.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org