[
https://issues.apache.org/jira/browse/IGNITE-23015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-23015:
---------------------------------------
Description: IgniteCatalog 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
RestartProofIgniteTables). (was: IgniteCatalog 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).)
> IgniteCatalog transparency wrt node restart
> -------------------------------------------
>
> Key: IGNITE-23015
> URL: https://issues.apache.org/jira/browse/IGNITE-23015
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3, inprocess-restart
>
> IgniteCatalog 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
> RestartProofIgniteTables).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
