[
https://issues.apache.org/jira/browse/SPARK-33427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-33427.
---------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
Issue resolved by pull request 30341
[https://github.com/apache/spark/pull/30341]
> Interpreted subexpression elimination
> -------------------------------------
>
> Key: SPARK-33427
> URL: https://issues.apache.org/jira/browse/SPARK-33427
> Project: Spark
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: L. C. Hsieh
> Assignee: L. C. Hsieh
> Priority: Major
> Fix For: 3.1.0
>
>
> Currently we only do subexpression elimination for codegen. For some reasons,
> we may need to run interpreted expression valuation. For example, codegen
> fails to compile and fallback to interpreted mode. It is commonly seen for
> complex schema from expressions that is possibly caused by the query
> optimizer too, e.g. SPARK-32945.
> We should also support subexpression elimination for interpreted evaluation.
> That could reduce performance difference when Spark fallbacks from codegen to
> interpreted expression evaluation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
