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

[GLUTEN-5136][VL] Duplicated output from Spark-to-Velox broadcast relation conversion #5141

Merged
merged 2 commits into from
Mar 27, 2024

Conversation

zhztheplayer
Copy link
Member

#5136

Will be tested by #5058. It's probably not a trivial code path and may delay adding dedicated UTs.

Copy link

#5136

@zhztheplayer
Copy link
Member Author

cc @ulysses-you

@zhztheplayer zhztheplayer merged commit e4fe9ba into apache:main Mar 27, 2024
12 checks passed
@ulysses-you
Copy link
Contributor

Thank you @zhztheplayer for the quick fix. After this pr if there is no c2r, the duplicate keys issue is still existed right ?

@zhztheplayer
Copy link
Member Author

Thank you @zhztheplayer for the quick fix. After this pr if there is no c2r, the duplicate keys issue is still existed right ?

After the fix is applied we should no longer have any relevant issues on BHJ unless unknown.

The issue this PR tried to fix only happened when broadcast exchange is fallen back but bhj is not. Which is a corner case for current Gluten, usually they are both fallen back or both not. Thus ideally we shouldn't have this issue in usual bhj processing.

@ulysses-you
Copy link
Contributor

I see, thank you for the explaination!

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.

2 participants