[ 
https://issues.apache.org/jira/browse/SPARK-29013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

L. C. Hsieh resolved SPARK-29013.
---------------------------------
    Resolution: Won't Fix

> Structurally equivalent subexpression elimination
> -------------------------------------------------
>
>                 Key: SPARK-29013
>                 URL: https://issues.apache.org/jira/browse/SPARK-29013
>             Project: Spark
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: L. C. Hsieh
>            Priority: Major
>
> We do semantically equivalent subexpression elimination in SparkSQL. However, 
> for some expressions that are not semantically equivalent, but structurally 
> equivalent, current subexpression elimination generates too many similar 
> functions. These functions share same computation structure but only differ 
> in input slots of current processing row.
> For such expressions, we can generate just one function, and pass in input 
> slots during runtime.
> It can reduce the length of generated code text, and save compilation time.
>  



--
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

Reply via email to