{"push_id":916307825,"size":1,"distinct_size":1,"ref":"refs/heads/branch-1.6","head":"b8da77ef776ab9cdc130a70293d75e7bdcdf95b0","before":"865dd8bccfc994310ad6664151d469043706ef3b","commits":[{"sha":"b8da77ef776ab9cdc130a70293d75e7bdcdf95b0","author":{"email":"905db6c57c9ba2de5402239d136139da9b5d0058@gmail.com","name":"gatorsmile"},"message":"[SPARK-12520] [PYSPARK] Correct Descriptions and Add Use Cases in Equi-Join\n\nAfter reading the JIRA https://issues.apache.org/jira/browse/SPARK-12520, I double checked the code.\n\nFor example, users can do the Equi-Join like\n  ```df.join(df2, 'name', 'outer').select('name', 'height').collect()```\n- There exists a bug in 1.5 and 1.4. The code just ignores the third parameter (join type) users pass. However, the join type we called is `Inner`, even if the user-specified type is the other type (e.g., `Outer`).\n- After a PR: https://github.com/apache/spark/pull/8600, the 1.6 does not have such an issue, but the description has not been updated.\n\nPlan to submit another PR to fix 1.5 and issue an error message if users specify a non-inner join type when using Equi-Join.\n\nAuthor: gatorsmile <gatorsmile@gmail.com>\n\nCloses #10477 from gatorsmile/pyOuterJoin.","distinct":true,"url":"https://api.github.com/repos/apache/spark/commits/b8da77ef776ab9cdc130a70293d75e7bdcdf95b0"}]}