[
https://issues.apache.org/jira/browse/SPARK-35381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343006#comment-17343006
]
Apache Spark commented on SPARK-35381:
--------------------------------------
User 'HyukjinKwon' has created a pull request for this issue:
https://github.com/apache/spark/pull/32517
> Fix lambda variable name issues in nested DataFrame functions in R APIs
> -----------------------------------------------------------------------
>
> Key: SPARK-35381
> URL: https://issues.apache.org/jira/browse/SPARK-35381
> Project: Spark
> Issue Type: Bug
> Components: SparkR
> Affects Versions: 3.1.1
> Reporter: Hyukjin Kwon
> Priority: Critical
> Labels: correctness
>
> R's higher order functions also have the same problem with SPARK-34794:
> {code}
> df <- sql("SELECT array(1, 2, 3) as numbers, array('a', 'b', 'c') as letters")
> collect(select(
> df,
> array_transform("numbers", function(number) {
> array_transform("letters", function(latter) {
> struct(alias(number, "n"), alias(latter, "l"))
> })
> })
> ))
> {code}
> {code}
> transform(numbers, lambdafunction(transform(letters,
> lambdafunction(struct(namedlambdavariable() AS n, namedlambdavariable() AS
> l), namedlambdavariable())), namedlambdavariable()))
> 1
> a, a, b, b, c, c, a, a,
> b, b, c, c, a, a, b, b, c, c
> {code}
--
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
