You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/08 11:23:00 UTC
[jira] [Updated] (IGNITE-11325) SQL: Single place to start missing
caches (H2Utils.checkAndStartNotStartedCache)
[ https://issues.apache.org/jira/browse/IGNITE-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-11325:
-------------------------------------
Fix Version/s: (was: 2.8)
2.9
> SQL: Single place to start missing caches (H2Utils.checkAndStartNotStartedCache)
> --------------------------------------------------------------------------------
>
> Key: IGNITE-11325
> URL: https://issues.apache.org/jira/browse/IGNITE-11325
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Priority: Major
> Fix For: 2.9
>
>
> We need to start missing caches for the given SELECT/DML statement because we need affinity info during query planning which is only available for started caches.
> We need to do the following:
> # Move the method {{H2Utils.checkAndStartNotStartedCache}} to some common place, e.g. parser, so that it has one and only one usage all over the code base
> # Make sure that this method doesn't produce multiple network hops: missing caches should be started in a single request if possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)