Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-12520] [PySpark] Correct Descriptions and Add Use Cases in Equi-Join #10477

Closed
wants to merge 1 commit into from

Conversation

gatorsmile
Copy link
Member

After reading the JIRA https://issues.apache.org/jira/browse/SPARK-12520, I double checked the code.

For example, users can do the Equi-Join like
df.join(df2, 'name', 'outer').select('name', 'height').collect()

Plan 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.

@SparkQA
Copy link

SparkQA commented Dec 25, 2015

Test build #48327 has finished for PR 10477 at commit 2923182.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@gatorsmile
Copy link
Member Author

@davies @JoshRosen Could you check if this PR is appropriate? Thanks!

@davies
Copy link
Contributor

davies commented Dec 28, 2015

LGTM, merging into master and 1.6 (for doc). I think it's fine to not fix 1.5 branch, until some one hit it, because we may not have a new release for 1.5 branch.

asfgit pushed a commit that referenced this pull request Dec 28, 2015
…i-Join

After reading the JIRA https://issues.apache.org/jira/browse/SPARK-12520, I double checked the code.

For example, users can do the Equi-Join like
  ```df.join(df2, 'name', 'outer').select('name', 'height').collect()```
- 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`).
- After a PR: #8600, the 1.6 does not have such an issue, but the description has not been updated.

Plan 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.

Author: gatorsmile <[email protected]>

Closes #10477 from gatorsmile/pyOuterJoin.
@asfgit asfgit closed this in 9ab296e Dec 28, 2015
@gatorsmile
Copy link
Member Author

Thank you!

@gatorsmile gatorsmile deleted the pyOuterJoin branch December 28, 2015 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants