[
https://issues.apache.org/jira/browse/SPARK-47001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-47001.
---------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 45146
[https://github.com/apache/spark/pull/45146]
> Pushdown Verification in Optimizer.scala should support changed data types
> --------------------------------------------------------------------------
>
> Key: SPARK-47001
> URL: https://issues.apache.org/jira/browse/SPARK-47001
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.3.0
> Reporter: Holden Karau
> Assignee: Holden Karau
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> When pushing a filter down in a union the data type may not match exactly if
> the filter was constructed using the child dataframe reference. This is
> because the unions output is updated with a structype merge of union which
> can turn non-nullable to nullable. These are still the same column despite
> the different nullability so the filter should be safe to push down. As it
> currently stands we get an exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
