[
https://issues.apache.org/jira/browse/SPARK-44137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SPARK-44137:
-----------------------------------
Labels: pull-request-available (was: )
> Change handling of iterable objects for on field in joins
> ---------------------------------------------------------
>
> Key: SPARK-44137
> URL: https://issues.apache.org/jira/browse/SPARK-44137
> Project: Spark
> Issue Type: Improvement
> Components: PySpark
> Affects Versions: 3.5.0
> Reporter: John Haberstroh
> Priority: Minor
> Labels: pull-request-available
>
> The {{on}} field complained when I passed it a Tuple. That's because it saw
> that it checked for {{list}} exactly, and so wrapped it into a list like
> {{{}[on]{}}}, leading to immediate failure. This was surprising -- typically,
> tuple and list should be interchangeable, and typically tuple is the more
> readily accepted type. I have proposed a change that moves towards the
> principle of least surprise for this situation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
