[
https://issues.apache.org/jira/browse/IGNITE-27640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-27640:
---------------------------------------
Description:
Currently both read-write and read-only transactions are inherited from common
InternalTransaction interface. This complicates adding the logic on interface
level, which is applicable only to specific type of transaction.
We need to split InternalTransaction to InternalReadOnlyTransaction and
InternalReadWriteTransaction, having distinct set of methods, applicable to a
specific type of a transaction.
Common methods remain in InternalTransaction
was:
Currently both read-write and read-only transactions are inherited from common
InternalTransaction interface. This complicates adding the logic on interface
level, which is applicable only to specific type of transaction.
We need to split InternalTransaction to InternalReadOnlyTransaction and
InternalReadWriteTransaction, having distinct set of methods, applicable to a
specific type of a transaction.
> Refactor InternalTransaction to better reflect transaction properties
> ---------------------------------------------------------------------
>
> Key: IGNITE-27640
> URL: https://issues.apache.org/jira/browse/IGNITE-27640
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3
>
> Currently both read-write and read-only transactions are inherited from
> common InternalTransaction interface. This complicates adding the logic on
> interface level, which is applicable only to specific type of transaction.
> We need to split InternalTransaction to InternalReadOnlyTransaction and
> InternalReadWriteTransaction, having distinct set of methods, applicable to a
> specific type of a transaction.
> Common methods remain in InternalTransaction
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
