Revert "fix(expr-common): Coerce to Decimal(20, 0) when combining UInt64 with signed integers (#14223)"#14292
Closed
alamb wants to merge 1 commit intoapache:mainfrom
Closed
Revert "fix(expr-common): Coerce to Decimal(20, 0) when combining UInt64 with signed integers (#14223)"#14292alamb wants to merge 1 commit intoapache:mainfrom
alamb wants to merge 1 commit intoapache:mainfrom
Conversation
…t64 with signed integers (apache#14223)" This reverts commit e0f9f65.
This was referenced Jan 25, 2025
Contributor
Author
|
I think we decided we don't need to do this |
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
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.
Draft PR to test the performance implications of #14223.
Which issue does this PR close?
Rationale for this change
There is concern that #14223 will slow down performance
I would like to gather some real data to find out, so I am preparing a branch to test.
I don't know yet if I will propose to merge thisUpdate, my measurements suggest there is no change in benchmark performance
What changes are included in this PR?
Reverts
Are these changes tested?
I ran benchmark results;
Clickbench
TPCH
Are there any user-facing changes?