-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[fix](Nereids) change numeric arithmatic function boundary behavior to match with be execution behavior #47966
[fix](Nereids) change numeric arithmatic function boundary behavior to match with be execution behavior #47966
Conversation
…o match with be execution behavior
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
// testFoldConst("SELECT COSH(1E308)") | ||
// testFoldConst("SELECT COSH(-1E308)") |
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.
why comments?
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.
COSH/POWER/DEGREES functions would meet inf problem when input is to large, be execute need to fix it
run buildall |
TPC-H: Total hot run time: 31424 ms
|
TPC-DS: Total hot run time: 183004 ms
|
ClickBench: Total hot run time: 30.35 s
|
run buildall |
TPC-H: Total hot run time: 31559 ms
|
TPC-DS: Total hot run time: 190565 ms
|
ClickBench: Total hot run time: 30.02 s
|
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
PR approved by anyone and no changes requested. |
PR approved by at least one committer and no changes requested. |
…o match with be execution behavior (#47966) ### What problem does this PR solve? Related PR: #40744, #47228 Problem Summary: When numeric function input or output out of boundary when fe folding constant, it would throw an exception before. Now we change it to match with be execution result, which is NullLiteral
…o match with be execution behavior (apache#47966) ### What problem does this PR solve? Related PR: apache#40744, apache#47228 Problem Summary: When numeric function input or output out of boundary when fe folding constant, it would throw an exception before. Now we change it to match with be execution result, which is NullLiteral
…o match with be execution behavior (apache#47966) Related PR: apache#40744, apache#47228 Problem Summary: When numeric function input or output out of boundary when fe folding constant, it would throw an exception before. Now we change it to match with be execution result, which is NullLiteral
…o match with be execution behavior (apache#47966) ### What problem does this PR solve? Related PR: apache#40744, apache#47228 Problem Summary: When numeric function input or output out of boundary when fe folding constant, it would throw an exception before. Now we change it to match with be execution result, which is NullLiteral
…y behavior to match with be execution behavior #47966 (#48237) pick:#47966 Related PR: #40744, #47228 Problem Summary: When numeric function input or output out of boundary when fe folding constant, it would throw an exception before. Now we change it to match with be execution result, which is NullLiteral ### What problem does this PR solve? Issue Number: close #xxx Related PR: #xxx Problem Summary: ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [ ] Regression test - [ ] Unit Test - [ ] Manual test (add detailed scripts or steps below) - [ ] No need to test or manual test. Explain why: - [ ] This is a refactor/code format and no logic has been changed. - [ ] Previous test can cover this change. - [ ] No code files have been changed. - [ ] Other reason <!-- Add your reason? --> - Behavior changed: - [ ] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [ ] No. - [ ] Yes. <!-- Add document PR link here. eg: apache/doris-website#1214 --> ### Check List (For Reviewer who merge this PR) - [ ] Confirm the release note - [ ] Confirm test cases - [ ] Confirm document - [ ] Add branch pick label <!-- Add branch pick label that this PR should merge into -->
…y behavior to match with be execution behavior (#47966) (#48281) pick:#47966 ### What problem does this PR solve? Related PR: #40744, #47228 Problem Summary: When numeric function input or output out of boundary when fe folding constant, it would throw an exception before. Now we change it to match with be execution result, which is NullLiteral
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #40744, #47228
Problem Summary:
When numeric function input or output out of boundary when fe folding constant, it would throw an exception before. Now
we change it to match with be execution result, which is NullLiteral
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)