[ 
https://issues.apache.org/jira/browse/IGNITE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yury Gerzhedovich reassigned IGNITE-20476:
------------------------------------------

    Assignee: Yury Gerzhedovich

> improve checking SQL exceptions in tests
> ----------------------------------------
>
>                 Key: IGNITE-20476
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20476
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Yury Gerzhedovich
>            Assignee: Yury Gerzhedovich
>            Priority: Major
>              Labels: ignite-3
>
> As of now there are few different approaches to check exception from 
> SQLengine. It leads to hard control exceptions handling, like that all public 
> Exception should be really public and don't belong to internal packages, or 
> that all public exceptions have a text messages.
>  Let's move all exceptions checks related to SQL to two main points:
> 1) SqlTestUtils.assertThrowsSqlException(...) methods for SQL API
> 2) JdbcTestUtils.assertThrowsSqlException(...) methods fro JDBC API



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to