[
https://issues.apache.org/jira/browse/IGNITE-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-20342:
----------------------------------------
Fix Version/s: 3.0.0-beta2
> 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
> Fix For: 3.0.0-beta2
>
> Time Spent: 3h
> 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)
