[
https://issues.apache.org/jira/browse/IGNITE-27491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-27491:
--------------------------------------
Description:
Currently queries planning is dependent on catalog version. In case of any
catalog change, even if it is not related to the current SQL query, the query
optimization will be performed anew.
It is even worse if the catalog was changed during planning, in which case we
will have to reschedule the planning one more time.
We need to figure out how to avoid re-planning of the SQL query if the catalog
has been changed, but these changes are unrelated to the current query.
was:
Currently queries planning is dependent on catalog version. In case of any
catalog change, even if it is not related to the current SQL query, the query
optimization will be performed anew.
It is even worse if the catalog changes during planning, in which case we will
reschedule the planning one more time.
We need to figure out how to avoid re-planning of the SQL query if the catalog
has been changed, but these changes are unrelated to the current query.
> Sql. Avoid re-planning in case of unreletad catalog changes
> -----------------------------------------------------------
>
> Key: IGNITE-27491
> URL: https://issues.apache.org/jira/browse/IGNITE-27491
> Project: Ignite
> Issue Type: Improvement
> Components: sql ai3
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> Currently queries planning is dependent on catalog version. In case of any
> catalog change, even if it is not related to the current SQL query, the query
> optimization will be performed anew.
> It is even worse if the catalog was changed during planning, in which case we
> will have to reschedule the planning one more time.
> We need to figure out how to avoid re-planning of the SQL query if the
> catalog has been changed, but these changes are unrelated to the current
> query.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
