[
https://issues.apache.org/jira/browse/IGNITE-17473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-17473:
--------------------------------------
Description:
We need to support transactional scan in SQL engine.
At the moment, the transactional protocol has a restriction such that the scan
must be initiated on the node that initiated the transaction. This makes
optimisations related to a distributed sql execution barely usable, but we will
deal with this later. As a first step, let's just disable distribution trait in
the planner to get a local plans.
was:
Right now transaction not sending to remote nodes, so we don't use single
transaction for whole query (transaction scan is not possible).
Need to transfer transaction metadata to remote nodes and use it during scan.
Seems required transfer just transaction id and recover transaction by the id
(build transaction instance limited transaction, don't go to transaction
coordinator) on remote nodes, however need to understand should we do enlist
partitions for scan.
Start point:
org.apache.ignite.internal.sql.engine.exec.rel.TableScanNode#request
> Support transactional scan for RW transaction
> ---------------------------------------------
>
> Key: IGNITE-17473
> URL: https://issues.apache.org/jira/browse/IGNITE-17473
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> We need to support transactional scan in SQL engine.
> At the moment, the transactional protocol has a restriction such that the
> scan must be initiated on the node that initiated the transaction. This makes
> optimisations related to a distributed sql execution barely usable, but we
> will deal with this later. As a first step, let's just disable distribution
> trait in the planner to get a local plans.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
