You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Gengliang Wang (Jira)" <ji...@apache.org> on 2022/03/01 01:41:00 UTC

[jira] [Resolved] (SPARK-38347) Nullability propagation in transformUpWithNewOutput

     [ https://issues.apache.org/jira/browse/SPARK-38347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gengliang Wang resolved SPARK-38347.
------------------------------------
    Fix Version/s: 3.3.0
                   3.2.2
       Resolution: Fixed

Issue resolved by pull request 35685
[https://github.com/apache/spark/pull/35685]

> 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
>            Assignee: Yingyi Bu
>            Priority: Major
>             Fix For: 3.3.0, 3.2.2
>
>
> 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