chore: Upgrade datafusion to version 49 #1200
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for taking this on! I was just thinking today it was time to kick off the 49 release. I suspect that failing test is due to the upstream changes. |
Yes, the specific bug causing the errors is being tracked here: apache/datafusion#17011. |
|
Looks like the new clippy version is complaining. We had to make these same changes in other repos |
|
@timsaucer should be ready now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
N/A.
Rationale for this change
Upgrades to the latest version of
datafusionand related crates.Marked as a draft for now while we wait for
49.0.1, which fixes a bug that is causing some tests to fail: apache/datafusion#17036.What changes are included in this PR?
datafusionand related crates to version 49.Are there any user-facing changes?
The Python API remains the same. One thing to notice is that
md5type is nowstring_viewinstead ofstring.