-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Add type coercion rule for concat and concat_ws
#3721
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
14e145a
concat type coercion
HaoYang670 586329a
Merge remote-tracking branch 'upstream/master' into 3720_type_coercio…
HaoYang670 a459c58
fix test
HaoYang670 1adfe58
Merge remote-tracking branch 'upstream/master' into 3720_type_coercio…
HaoYang670 354be11
use builder function
HaoYang670 63c2587
Merge remote-tracking branch 'upstream/master' into 3720_type_coercio…
HaoYang670 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
I wonder if we should do something with
LargeUtf8?Also, would it make sense to check the types before
clone()ing them to do a cast that might not be needed?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.
I think this has been done in the
cast_tofunction: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.
This is a good suggestion. My opinion is that we could use
LargeUtf8if one of the arguments has this type.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.
Is there type coercion rule for the function
ConcatorConcatWithSeparator?Now the type coercion are not supported in the logical phase for some expr which is
Expr::ScalarFunction,Expr::AggregateFunction,Expr::WindowFunctionandExpr::AggregateUDFin the follow-up pr for this #3582 (comment)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.
I think after moving the
type coercionrule to the logical phase, this issue can be resolvedThere 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.
I am not sure what you mean about "type coercion rule for the function Concat or ConcatWithSeparator"
Since it is a
Expr::ScalarFunction { fun, args }it currently gets coerced usingdata_typeshttps://github.com/apache/arrow-datafusion/blob/3eb55e9a0510d872f6f7765b1a5f17db46486e45/datafusion/expr/src/type_coercion.rs#L44-L47Are you suggesting we move the logic that picks what argument types (in this case string) for concat into
data_types? (I think this is a good idea, for the record)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.
Yes, we can do it in the #3582 (comment)
And this pr can be merged first.