[
https://issues.apache.org/jira/browse/IGNITE-19493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-19493:
-------------------------------------
Description:
As of now, in SqlQueryProcessor.querySingle0(), we get SQL SchemaPlus from
SqlQueryManager, then create query context, then start implicit transaction if
needed.
SqlQueryManager doesn't aware of schema versions.
Let's
* add tx timestamp to the interface, it is ok to ignore the tx timestamp
parameter in current implementation unless a new one based on Catalog will be
implemented in IGNITE-19496.
* rework current flow to start implicit transaction first, then get a schema
based on Tx timestamp, then create a query context.
was:
As of now, in SqlQueryProcessor.querySingle0(), we get SQL SchemaPlus from
SqlQueryMaanger, then create query context, then start implicit transaction if
needed.
SqlQueryManager doesn't aware of schema versions.
Let's
* add tx timestamp to the interface, it is ok to ignore the tx timestamp
parameter in current implementation unless a new one based on Catalog will be
implemented in IGNITE-19496.
* rework current flow to start implicit transaction first, then get a schema
based on Tx timestamp, then create a query context.
> Sql. Query flow refactoring.
> ----------------------------
>
> Key: IGNITE-19493
> URL: https://issues.apache.org/jira/browse/IGNITE-19493
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
>
> As of now, in SqlQueryProcessor.querySingle0(), we get SQL SchemaPlus from
> SqlQueryManager, then create query context, then start implicit transaction
> if needed.
> SqlQueryManager doesn't aware of schema versions.
> Let's
> * add tx timestamp to the interface, it is ok to ignore the tx timestamp
> parameter in current implementation unless a new one based on Catalog will be
> implemented in IGNITE-19496.
> * rework current flow to start implicit transaction first, then get a schema
> based on Tx timestamp, then create a query context.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
