-
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
Minor: comments about coercion in physical planner #4745
Conversation
@liukun4515 already made This one has some improved comments, so I'll plan to polish it up once |
expressions::cast(rhs, input_schema, target_datatype)?, | ||
input_schema, | ||
) | ||
// Note that the logical planner is responsible |
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.
👍
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 for your comments
fe730c1
to
23b140b
Compare
I plan to merge this PR once CI has passed |
Benchmark runs are scheduled for baseline = fc8fb06 and contender = 3abbffb. 3abbffb is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Which issue does this PR close?
As pointed out by @liukun4515 on #4726 #4726 (comment) type coercion is not needed during physical planning
cc @comphead
Rationale for this change
Code is uneededAvoid confusion about design in the future
What changes are included in this PR?
Remove uneeded codeAdd comments about coercion in the physical planner
Are these changes tested?
Yes, all existing tests pass
Are there any user-facing changes?
No