[
https://issues.apache.org/jira/browse/IGNITE-20388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-20388:
---------------------------------------
Description:
ClusterPerClassIntegrationTest provides convenient shortcuts to run sql queries
{{ClusterPerClassIntegrationTest#sql}}). This shortcuts are used to prepare
cluster to run certain statements as well as validate in case of errors certain
exceptions are raised.
The problem is that both these shortcuts uses internal api under the hood, and
internal api doesn't have exception conversion (by design). With that said,
it's possible to get {{CatalogValidationException}} where SqlException with
code STMT_VALIDATION_ERR was expected.
Since vast majority of the tests using those shortcuts have e2e semantic, it's
better to change implementation of the shortcuts to use public api instead.
Tests that relies on internal api semantic, if any, should be reworked to use
different shortcuts.
was:
ClusterPerClassIntegrationTest provides convenient shortcuts to run sql queries
{{ClusterPerClassIntegrationTest#sql}}). This shortcuts are used to prepare
cluster to run certain statements as well as validate in case of errors certain
exceptions are raised.
The problem is that both these shortcuts uses internal api under the hood, and
internal api doesn't have exception conversion (by design). With that said,
it's possible to get {{CatalogValidationException}} where SqlException with
code STMT_VALIDATION_ERR was expected.
Since vast majority of the tests using those shortcuts have e2e semantic, it's
better to change implementation of the shortcuts to use public api instead.
Tests that relies on internal api semantic, if any, should be reworked to use
different shortcuts.
> Sql. Migrate ClusterPerClassIntegrationTest to run queries via public api
> -------------------------------------------------------------------------
>
> Key: IGNITE-20388
> URL: https://issues.apache.org/jira/browse/IGNITE-20388
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> ClusterPerClassIntegrationTest provides convenient shortcuts to run sql
> queries {{ClusterPerClassIntegrationTest#sql}}). This shortcuts are used to
> prepare cluster to run certain statements as well as validate in case of
> errors certain exceptions are raised.
> The problem is that both these shortcuts uses internal api under the hood,
> and internal api doesn't have exception conversion (by design). With that
> said, it's possible to get {{CatalogValidationException}} where SqlException
> with code STMT_VALIDATION_ERR was expected.
> Since vast majority of the tests using those shortcuts have e2e semantic,
> it's better to change implementation of the shortcuts to use public api
> instead. Tests that relies on internal api semantic, if any, should be
> reworked to use different shortcuts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
