Perform type coercion for corr aggregate function during physical planning #15776
+650
−8
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
github-actions
bot
added
logical-expr
kumarlokesh
force-pushed
the
avoid-explicit-cast-in-corr-aggregate-fn
branch
from
41587c4 to
1933efe
Compare
kumarlokesh
force-pushed
the
avoid-explicit-cast-in-corr-aggregate-fn
branch
from
1933efe to
d8a7641
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
corraggregate function #13721.Rationale for this change
What changes are included in this PR?
apply_aggregate_coercionthat applies typecoercion during physical planning based on the logical type coercion rules
CorrelationGroupsAccumulator.update_batchmethodAre these changes tested?
Are there any user-facing changes?