-
Notifications
You must be signed in to change notification settings - Fork 93
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
IGNITE-23141 Sql. Add execution test to verify numeric type coercion in binary comparison and arithmetic #4382
Conversation
...est/java/org/apache/ignite/internal/sql/engine/exec/coercion/BaseTypeCheckExecutionTest.java
Outdated
Show resolved
Hide resolved
...java/org/apache/ignite/internal/sql/engine/exec/coercion/NumericComparisonExecutionTest.java
Show resolved
Hide resolved
...java/org/apache/ignite/internal/sql/engine/exec/coercion/NumericComparisonExecutionTest.java
Outdated
Show resolved
Hide resolved
...java/org/apache/ignite/internal/sql/engine/exec/coercion/NumericComparisonExecutionTest.java
Outdated
Show resolved
Hide resolved
@korlov42 , @ygerzhedovich gyus, i cut it into two (arithmetic and comparison) tests and change comparison results for more convenient usage in linkage with planner tests. So i prefer to merge it as is, after completion [1] additional issue need to be filled for planner results re-usage in executions tests. |
...est/java/org/apache/ignite/internal/sql/engine/exec/coercion/BaseTypeCheckExecutionTest.java
Outdated
Show resolved
Hide resolved
...ava/org/apache/ignite/internal/sql/engine/exec/coercion/NumericArithmeticsExecutionTest.java
Outdated
Show resolved
Hide resolved
@korlov42 , @ygerzhedovich is ready for review. |
...est/java/org/apache/ignite/internal/sql/engine/exec/coercion/BaseTypeCheckExecutionTest.java
Outdated
Show resolved
Hide resolved
...ava/org/apache/ignite/internal/sql/engine/exec/coercion/NumericArithmeticsExecutionTest.java
Outdated
Show resolved
Hide resolved
...ngine/src/test/java/org/apache/ignite/internal/sql/engine/planner/datatypes/utils/Types.java
Outdated
Show resolved
Hide resolved
...est/java/org/apache/ignite/internal/sql/engine/exec/coercion/BaseTypeCheckExecutionTest.java
Outdated
Show resolved
Hide resolved
...ava/org/apache/ignite/internal/sql/engine/exec/coercion/NumericArithmeticsExecutionTest.java
Outdated
Show resolved
Hide resolved
...ava/org/apache/ignite/internal/sql/engine/exec/coercion/NumericArithmeticsExecutionTest.java
Outdated
Show resolved
Hide resolved
...java/org/apache/ignite/internal/sql/engine/exec/coercion/NumericComparisonExecutionTest.java
Outdated
Show resolved
Hide resolved
.../test/java/org/apache/ignite/internal/sql/engine/planner/datatypes/BaseTypeCoercionTest.java
Outdated
Show resolved
Hide resolved
.../test/java/org/apache/ignite/internal/sql/engine/planner/datatypes/BaseTypeCoercionTest.java
Outdated
Show resolved
Hide resolved
...est/java/org/apache/ignite/internal/sql/engine/exec/coercion/BaseTypeCheckExecutionTest.java
Outdated
Show resolved
Hide resolved
...est/java/org/apache/ignite/internal/sql/engine/exec/coercion/BaseTypeCheckExecutionTest.java
Show resolved
Hide resolved
...est/java/org/apache/ignite/internal/sql/engine/exec/coercion/BaseTypeCheckExecutionTest.java
Outdated
Show resolved
Hide resolved
&& (result.getClass() != Double.class) | ||
&& (result.getClass() != Boolean.class); | ||
|
||
boolean precisionScale = true; |
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.
maybe precisionScaleMatched
?
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.
done
Thank you for submitting the pull request.
To streamline the review process of the patch and ensure better code quality
we ask both an author and a reviewer to verify the following:
The Review Checklist
- There is a single JIRA ticket related to the pull request.
- The web-link to the pull request is attached to the JIRA ticket.
- The JIRA ticket has the Patch Available state.
- The description of the JIRA ticket explains WHAT was made, WHY and HOW.
- The pull request title is treated as the final commit message. The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
Notes