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

fix: SortMergeJoin with unsupported key type should fall back to Spark #355

Merged
merged 4 commits into from
Apr 30, 2024

Conversation

viirya
Copy link
Member

@viirya viirya commented Apr 30, 2024

Which issue does this PR close?

Closes #354.

Rationale for this change

What changes are included in this PR?

How are these changes tested?

@viirya
Copy link
Member Author

viirya commented Apr 30, 2024

cc @sunchao @andygrove

Copy link
Member

@andygrove andygrove left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @viirya

@planga82
Copy link
Contributor

As an idea, I was thinking that we could put in tests to check the supported types in Datafusion, so that when we upgrade to a version of datafusion that supports these other types (like timestamp with timezone for example) we are aware that we should change the list of allowed types.

@viirya viirya merged commit 7067606 into apache:main Apr 30, 2024
28 checks passed
@viirya
Copy link
Member Author

viirya commented Apr 30, 2024

Merged. Thanks.

@viirya
Copy link
Member Author

viirya commented May 1, 2024

@planga82 Thanks for the suggestion. I created an issue to track it.

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.

SortMergeJoin with unsupported key type should fall back to Spark
4 participants