You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2023/12/04 15:21:00 UTC
[jira] [Updated] (IGNITE-21018) Sql. Introduce cache for plan mapping
[ https://issues.apache.org/jira/browse/IGNITE-21018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Orlov updated IGNITE-21018:
--------------------------------------
Labels: ignite-3 (was: )
> Sql. Introduce cache for plan mapping
> -------------------------------------
>
> Key: IGNITE-21018
> URL: https://issues.apache.org/jira/browse/IGNITE-21018
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> Mapping query on cluster topology is fairly expensive operation, because it requires acquiring replicas per every partition a traversing a plan tree in order to compute colocation of a query fragment.
> This problem can be mitigated by introducing a cache for mapped queries.
> Implementation notes: do not forget to invalidate cache when partition lease got expired or logical topology has been changed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)