[
https://issues.apache.org/jira/browse/IGNITE-24233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-24233:
---------------------------------------
Description:
When a transaction is aborted by Ignite (for example, by timeout) and not the
user, an attempt to commit a transaction should fail to signal to the user that
the transaction effects are not persisted.
Note that since IGNITE-23980 the following is maintained: only first
commit/rollback by the user on a transaction may throw an exception. This issue
is about another scenario, when 'first abort' is made by Ignite itself, so the
rule from IGNITE-23980 is not applicable and the subsequent commit() should
throw an exception (as, from the point of view of the user, it's first attempt
to finish the transaction).
was:When a transaction is aborted by Ignite (for example, by timeout) and not
the user, an attempt to commit a transaction should fail to signal to the user
that the transaction effects are not persisted.
> Fail commit on a transaction aborted by Ignite
> ----------------------------------------------
>
> Key: IGNITE-24233
> URL: https://issues.apache.org/jira/browse/IGNITE-24233
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> When a transaction is aborted by Ignite (for example, by timeout) and not the
> user, an attempt to commit a transaction should fail to signal to the user
> that the transaction effects are not persisted.
> Note that since IGNITE-23980 the following is maintained: only first
> commit/rollback by the user on a transaction may throw an exception. This
> issue is about another scenario, when 'first abort' is made by Ignite itself,
> so the rule from IGNITE-23980 is not applicable and the subsequent commit()
> should throw an exception (as, from the point of view of the user, it's first
> attempt to finish the transaction).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
