-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
remove type coercion
for physical ScalarFunction
#3749
Conversation
@@ -58,23 +58,20 @@ pub fn create_physical_expr( | |||
input_schema: &Schema, | |||
execution_props: &ExecutionProps, | |||
) -> Result<Arc<dyn PhysicalExpr>> { | |||
let coerced_phy_exprs = |
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.
remove type coercion in the physical phase
@@ -310,18 +310,6 @@ impl ExprRewriter for TypeCoercionRewriter { | |||
}; | |||
Ok(expr) | |||
} | |||
Expr::ScalarUDF { fun, args } => { |
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.
just move these code
60e1787
to
b9799e0
Compare
type coercion
for ScalarFunctiontype coercion
for ScalarFunction
type coercion
for ScalarFunctiontype coercion
for physical ScalarFunction
The CI checks appear to be failing |
b9799e0
to
00f2d31
Compare
Some errors about import in the test, I have fixed them PTAL @alamb |
I will merge it first, and not block the follow-up pr. |
Benchmark runs are scheduled for baseline = e54110f and contender = a92119a. a92119a is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
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.
LGTM. Thanks @liukun4515
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.
Looks good to me -- thanks @liukun4515
@@ -2872,4 +2874,17 @@ mod tests { | |||
|
|||
Ok(()) | |||
} | |||
|
|||
// Helper function | |||
// The type coercion will be done in the logical phase, should do the type coercion for the test |
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.
👍
BTW this is basically what I need to do in IOx / why I made #3708
Which issue does this PR close?
Closes #3731
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?