You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/03/17 09:27:00 UTC
[jira] [Updated] (SPARK-27935) Introduce leftOuterJoinWith and
fullOuterJoinWith
[ https://issues.apache.org/jira/browse/SPARK-27935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun updated SPARK-27935:
----------------------------------
Affects Version/s: (was: 3.0.0)
3.1.0
> Introduce leftOuterJoinWith and fullOuterJoinWith
> -------------------------------------------------
>
> Key: SPARK-27935
> URL: https://issues.apache.org/jira/browse/SPARK-27935
> Project: Spark
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Spencer
> Priority: Minor
>
> Currently, calling *Dataset[A].joinWith(Dataset[B], col, "left_outer")* or *Dataset[A].joinWith(Dataset[B], col, "full_outer")* require users to do null checks on the resulting *Dataset[(A, B)]*
>
> To make the expected result types of outer joins more explicit, I propose a couple of new joinWith functions:
> {noformat}
> def leftOuterJoinWith[U](other: Dataset[U], condition: Column): Dataset[(T, Option[U])]
> def fullOuterJoinWith[U](other: Dataset[U], condition: Column): Dataset[(Option[T], Option[U])]{noformat}
>
> The return type of *fullOuterJoinWith* is imperfect, since *(None, None)* is an invalid case, but still an improvement on the present interface.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org