Skip to content
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

Merged
merged 25 commits into from
Oct 8, 2024

Conversation

zstan
Copy link
Contributor

@zstan zstan commented Sep 12, 2024

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

  • Formal criteria: TC status, codestyle, mandatory documentation. Also make sure to complete the following:
    - 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.
  • Design: new code conforms with the design principles of the components it is added to.
  • Patch quality: patch cannot be split into smaller pieces, its size must be reasonable.
  • Code quality: code is clean and readable, necessary developer documentation is added if needed.
  • Tests code quality: test set covers positive/negative scenarios, happy/edge cases. Tests are effective in terms of execution time and resources.

Notes

@zstan
Copy link
Contributor Author

zstan commented Sep 17, 2024

@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.
[1] https://issues.apache.org/jira/browse/IGNITE-23192

@zstan
Copy link
Contributor Author

zstan commented Oct 2, 2024

@korlov42 , @ygerzhedovich is ready for review.

&& (result.getClass() != Double.class)
&& (result.getClass() != Boolean.class);

boolean precisionScale = true;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe precisionScaleMatched?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@zstan zstan merged commit e403426 into apache:main Oct 8, 2024
1 check passed
@zstan zstan deleted the ignite-23141 branch October 8, 2024 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants