Re: right outer joins on Datasets

2016-05-24 Thread Zhan
The first item as a whole should be null please refer to the jira. Sent from my iPhone > On May 24, 2016, at 7:31 AM, Koert Kuipers wrote: > > got it, but i assume thats an internal implementation detail, and it should > show null not -1? > >> On Tue, May 24, 2016 at 3:10 AM, Zhan Zhang wro

Re: right outer joins on Datasets

2016-05-24 Thread Koert Kuipers
got it, but i assume thats an internal implementation detail, and it should show null not -1? On Tue, May 24, 2016 at 3:10 AM, Zhan Zhang wrote: > The reason for "-1" is that the default value for Integer is -1 if the > value > is null > > def defaultValue(jt: String): String = jt match { >

Re: right outer joins on Datasets

2016-05-24 Thread Zhan Zhang
The reason for "-1" is that the default value for Integer is -1 if the value is null def defaultValue(jt: String): String = jt match { ... case JAVA_INT => "-1" ... } -- View this message in context: http://apache-spark-developers-list.1001551.n3.nabble.com/right-outer-joins-

Re: right outer joins on Datasets

2016-05-20 Thread Reynold Xin
I filed https://issues.apache.org/jira/browse/SPARK-15441 On Thu, May 19, 2016 at 8:48 AM, Andres Perez wrote: > Hi all, I'm getting some odd behavior when using the joinWith > functionality for Datasets. Here is a small test case: > > val left = List(("a", 1), ("a", 2), ("b", 3), ("c", 4)).