[
https://issues.apache.org/jira/browse/SPARK-35636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Feng updated SPARK-35636:
-------------------------------
Summary: Do not push down extract value in higher order function that
references both sides of a join (was: Do not push lambda variables out of
lambda functions in NestedColumnAliasing)
> Do not push down extract value in higher order function that references both
> sides of a join
> --------------------------------------------------------------------------------------------
>
> Key: SPARK-35636
> URL: https://issues.apache.org/jira/browse/SPARK-35636
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Karen Feng
> Priority: Major
>
> Currently, lambda keys can be referenced outside of the lambda function:
> {quote}Project [transform(keys#0, lambdafunction(_extract_v1#0, lambda key#0,
> false)) AS a#0]
> +- 'Join Cross
> :- Project [kvs#0[lambda key#0].v1 AS _extract_v1#0]
> : +- LocalRelation <empty>, [kvs#0]
> +- LocalRelation <empty>, [keys#0]{quote}
> This should be unchanged from the original state:
> {quote}Project [transform(keys#418, lambdafunction(kvs#417[lambda
> key#420].v1, lambda key#420, false)) AS a#419]
> +- Join Cross
> :- LocalRelation <empty>, [kvs#417]
> +- LocalRelation <empty>, [keys#418]{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
