[
https://issues.apache.org/jira/browse/IGNITE-20167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-20167:
--------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> Query execution flow uses catalog version.
> ------------------------------------------
>
> Key: IGNITE-20167
> URL: https://issues.apache.org/jira/browse/IGNITE-20167
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> As for now, we misuse SqlSchemaManager methods to get schema.
> 1. We should always use a version that is visible to current transaction at
> query start, instead of getting the latest one.
> 2. We wait for actual version on remote side, and then try to get latest
> version. However, we already know the required version and must use it.
> 3. Caching query plans must use version as well.
> Also, there is a bug IgniteSchemaTable.unwrap method, we should be able to
> unwrap table descriptor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
