-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat: The "character_length" function handle "Binary" type #7350
Conversation
Thanks for working on this @parkma99. The fix works great ! |
let args: Vec<ColumnarValue> = args | ||
.iter() | ||
.map(|col_value| { | ||
cast_column(col_value, &DataType::Utf8, None).unwrap() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In there ,I do not know how to handle this unwrap
.
Perhaps we could implement this as part of the coercion rules as opposed to internal to the evaluation logic? See coerce_arguments_for_fun perhaps? |
Thank you, it looks good, I will have a try lately |
I think it is a good solution. What do you think @tustvold ? |
Responded on the linked ticket |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for working on this @parkma99 and @JayjeetAtGithub
Can we please add a .slt level test for this functionality?
I think there is a single coercion rule change (the same as https://github.com/apache/arrow-datafusion/pull/7365/files#r1303360870) that will fix this issue as well
Which issue does this PR close?
Closes #7344
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?