You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "jiaan.geng (Jira)" <ji...@apache.org> on 2023/03/04 03:00:00 UTC

[jira] [Comment Edited] (SPARK-42562) UnresolvedLambdaVariables in python do not need unique names

    [ https://issues.apache.org/jira/browse/SPARK-42562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696390#comment-17696390 ] 

jiaan.geng edited comment on SPARK-42562 at 3/4/23 2:59 AM:
------------------------------------------------------------

[~hvanhovell] I don't understand this issue. Could you tell me where UnresolvedLambdaVariables need unique names in python ?


was (Author: beliefer):
[~hvanhovell]I don't understand this issue. Could you tell me where UnresolvedLambdaVariables need unique names in python ?

> UnresolvedLambdaVariables in python do not need unique names
> ------------------------------------------------------------
>
>                 Key: SPARK-42562
>                 URL: https://issues.apache.org/jira/browse/SPARK-42562
>             Project: Spark
>          Issue Type: New Feature
>          Components: Connect
>    Affects Versions: 3.4.0
>            Reporter: Herman van Hövell
>            Priority: Major
>
> UnresolvedLambdaVariables do not need unique names in python. We already did this for the scala client, and it is good to have parity between the two implementations.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org