You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "L. C. Hsieh (Jira)" <ji...@apache.org> on 2021/06/30 05:15:00 UTC
[jira] [Resolved] (SPARK-35829) Clean up evaluates subexpressions
and add more flexibility to evaluate particular subexpressoin
[ https://issues.apache.org/jira/browse/SPARK-35829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
L. C. Hsieh resolved SPARK-35829.
---------------------------------
Fix Version/s: 3.2.0
Resolution: Fixed
Issue resolved by pull request 32980
[https://github.com/apache/spark/pull/32980]
> Clean up evaluates subexpressions and add more flexibility to evaluate particular subexpressoin
> -----------------------------------------------------------------------------------------------
>
> Key: SPARK-35829
> URL: https://issues.apache.org/jira/browse/SPARK-35829
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.2.0
> Reporter: L. C. Hsieh
> Assignee: L. C. Hsieh
> Priority: Major
> Fix For: 3.2.0
>
>
> Currently `subexpressionEliminationForWholeStageCodegen` return` the gen-ed code of subexpressions. The caller simply puts the code into its code block. We need more flexible evaluation here. For example, for Filter operator's subexpression evaluation, we may need to evaluate particular subexpression for one predicate. Current approach cannot satisfy the requirement.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org