You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2024/08/17 08:56:00 UTC

[jira] [Updated] (IGNITE-23013) IgniteSql transparency wrt node restart

     [ https://issues.apache.org/jira/browse/IGNITE-23013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Puchkovskiy updated IGNITE-23013:
---------------------------------------
    Description: IgniteSql obtained in embedded mode via IgniteServer.api() should remain functional even after the node gets restarted (using in-process restart). This should work analogously to how it's done for IgniteTables (see IgniteTablesReference).

> IgniteSql transparency wrt node restart
> ---------------------------------------
>
>                 Key: IGNITE-23013
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23013
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3, inprocess-restart
>
> IgniteSql obtained in embedded mode via IgniteServer.api() should remain functional even after the node gets restarted (using in-process restart). This should work analogously to how it's done for IgniteTables (see IgniteTablesReference).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)