You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2022/08/10 06:26:00 UTC
[jira] [Assigned] (IGNITE-17434) Extend implicit sql transactions functionality for RO|RW transactions support.
[ https://issues.apache.org/jira/browse/IGNITE-17434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgeny Stanilovsky reassigned IGNITE-17434:
-------------------------------------------
Assignee: Evgeny Stanilovsky
> Extend implicit sql transactions functionality for RO|RW transactions support.
> ------------------------------------------------------------------------------
>
> Key: IGNITE-17434
> URL: https://issues.apache.org/jira/browse/IGNITE-17434
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 3.0.0-alpha5
> Reporter: Evgeny Stanilovsky
> Assignee: Evgeny Stanilovsky
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After [1] was implemented, there are some improvements seems still required:
> # If no explicit tx is specified it`s possible to obtain situation when keys from one bulk enlisted under different tx [2]
> # Implicit tx (not tx at all but tx meta - timestamp, first enlisted partition and so on ..) need to be replicated into all calcite execution fragments.
> Thus in [3] seems we need to start implicit tx if no explicit defined and correctly process it in [4]
> [1] https://issues.apache.org/jira/browse/IGNITE-17328
> [2] ModifyNode#flushTuples
> [3] ExecutionServiceImpl#executeQuery
> [4] DistributedQueryManager#execute
--
This message was sent by Atlassian Jira
(v8.20.10#820010)