You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Sapego (Jira)" <ji...@apache.org> on 2023/10/04 10:29:00 UTC
[jira] [Commented] (IGNITE-20342) Rollback transaction for SQL execution issues
[ https://issues.apache.org/jira/browse/IGNITE-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771805#comment-17771805 ]
Igor Sapego commented on IGNITE-20342:
--------------------------------------
Changes in ODBC tests looks good to me.
> Rollback transaction for SQL execution issues
> ---------------------------------------------
>
> Key: IGNITE-20342
> URL: https://issues.apache.org/jira/browse/IGNITE-20342
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> During execution any data modification we could have runtime error, for example divide to zero, which lead to cancellation of execution. Right now we don't rollback transaction for the case and part of modification could be applied despite of the error.
> In ideal word we should be rollbacked just the DML statement, but right now we don't support savepoint in transaction protocol. So, let's rollback any type of transaction, explicit and implicit, for any DML statement in case error is occurred.
> Test which could show one of the case of the problem is org.apache.ignite.internal.sql.api.ItSqlSynchronousApiTest#runtimeErrorInTransaction
--
This message was sent by Atlassian Jira
(v8.20.10#820010)