[
https://issues.apache.org/jira/browse/SPARK-34030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260162#comment-17260162
]
Apache Spark commented on SPARK-34030:
--------------------------------------
User 'ulysses-you' has created a pull request for this issue:
https://github.com/apache/spark/pull/31077
> Fold RepartitionExpression num partition should at Optimizer
> ------------------------------------------------------------
>
> Key: SPARK-34030
> URL: https://issues.apache.org/jira/browse/SPARK-34030
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.2.0
> Reporter: ulysses you
> Priority: Minor
>
> We meet some ploblem when backport SPARK-33806. It is because the
> UnresolvedFunction.foldable will throw a exception. It's ok with master
> branch, but it's better to do it at Optimizer. Some reason:
> # It's not always safe to call Expression.foldable before analysis.
> # fold num partition to 1 more like a optimize behavior.
--
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
