GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/22216
[SPARK-25223][SQL] Use a map to store values for NamedLambdaVariable.
## What changes were proposed in this pull request?
Currently we use `functionsForEval`, `NamedLambdaVarible`s in which are
replace with of arguments from the original functions, to make sure the lambda
variables refer the same instances as of arguments, but it's pretty hacky.
Instead, we can use a global map and set/get the lambda variable values in
the map.
## How was this patch tested?
Existing tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ueshin/apache-spark issues/SPARK-25223/use_map
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/22216.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #22216
----
commit 6dd5349ce8fca053432ebcea0d4699923fd1f15d
Author: Takuya UESHIN <ueshin@...>
Date: 2018-08-24T06:48:03Z
Move nullable to `SimpleHigherOrderFunction`.
commit c27121b8743fad106cd5cd2ce33d22814856ec9c
Author: Takuya UESHIN <ueshin@...>
Date: 2018-08-24T07:55:03Z
Use a map to store values for `NamedLambdaVariable`.
----
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
