You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2021/06/18 09:34:01 UTC
[jira] [Updated] (IGNITE-13846) Calcite improvements. Improve
possibility for handling topology change events.
[ https://issues.apache.org/jira/browse/IGNITE-13846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yury Gerzhedovich updated IGNITE-13846:
---------------------------------------
Labels: calcite2-required calcite3-required (was: )
> Calcite improvements. Improve possibility for handling topology change events.
> ------------------------------------------------------------------------------
>
> Key: IGNITE-13846
> URL: https://issues.apache.org/jira/browse/IGNITE-13846
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.9
> Reporter: Stanilovsky Evgeny
> Assignee: Stanilovsky Evgeny
> Priority: Major
> Labels: calcite2-required, calcite3-required
>
> For now we have equal logic in TableScan#reserve and IndexScan#reserve for partition reservation and have no possibility for remap|rerun query with new changed topology. As a starting point we can take already existing h2 logic containing in GridReduceQueryExecutor#query
--
This message was sent by Atlassian Jira
(v8.3.4#803005)