Takeshi Yamamuro commented on SPARK-23634:

Probably, this ticket is duplicate to 
In the previous discussion (https://github.com/apache/spark/pull/18576), adding 
a new rule for this purpose, it seems to be some intrusive, so we need to look 
for other approaches to solve this, I think.

> AttributeReferences may be too conservative wrt nullability after optimization
> ------------------------------------------------------------------------------
>                 Key: SPARK-23634
>                 URL: https://issues.apache.org/jira/browse/SPARK-23634
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.4.0
>            Reporter: Henry Robinson
>            Priority: Minor
> An {{AttributeReference}} effectively caches the nullability of its referent 
> when it is created. Some optimization rules can transform a nullable 
> attribute into a non-nullable one, but the references to it are not updated. 
> We could add a transformation rule that visits every {{AttributeReference}} 
> and fixes its nullability after optimization. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to