Fixed issue with md5 not support LargeUtf8 correctly #13502
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
alamb
approved these changes
Nov 20, 2024
| use DataType::*; | ||
| Ok(match &arg_types[0] { | ||
| LargeUtf8 | LargeBinary => LargeUtf8, | ||
| LargeUtf8 | LargeBinary => Utf8, |
Contributor
There was a problem hiding this comment.
Maybe as a follow on it should really be LargeUtf8 but then we would have to change the function I suppose
Contributor
|
Since this is a small code / bug fix merging it in now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
Dictionaryarrays such asmd5#13444Rationale for this change
Bug fix for md5 not working as expected with largeutf8 input
What changes are included in this PR?
Code, tests.
Are these changes tested?
Yes
Are there any user-facing changes?
No