You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Denis Chudov (Jira)" <ji...@apache.org> on 2025/11/21 12:29:00 UTC

[jira] [Updated] (IGNITE-27005) Add ability to set tx labels into public API

     [ https://issues.apache.org/jira/browse/IGNITE-27005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Chudov updated IGNITE-27005:
----------------------------------
    Epic Link: IGNITE-27132

> Add ability to set tx labels into public API
> --------------------------------------------
>
>                 Key: IGNITE-27005
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27005
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>
> *Motivation*
> Sometimes we need additional information to recognize a transaction and its origin. Tx ID doesn't contain this information. We need transaction labels like we had in Ignite 2.
> *Definition of done*
> Tx labels can be set in:
>  * IgniteTransactions: begin, beginAsync, runInTransaction, etc. via TransactionOptions.
>  * InternalTableImpl: scan, lookup via OperationContext/TxContext
> SQL should be covered by separate ticket.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)