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

Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2024/12/18 11:03:00 UTC

[jira] [Assigned] (IGNITE-23604) Implicit flag for SQL implicit transaction

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

Pavel Pereslegin reassigned IGNITE-23604:
-----------------------------------------

    Assignee: Pavel Pereslegin

> Implicit flag for SQL implicit transaction
> ------------------------------------------
>
>                 Key: IGNITE-23604
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23604
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Assignee: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> h3. Motivation
> The SQL engine creates an implicit transaction if no transaction was passed from outside (QueryTransactionContextImpl#getOrStartImplicit). The started transaction does not have an implicit flag because Table Manager is responsible for this transaction type (commit or rollback). But the SQL engine has to manage an implicit transaction themselves (SQL script may have more than one table operation).
>  
> h3. Definition of done
> Transactions that were created by SQL engine also need to have the implicit flag.



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