[
https://issues.apache.org/jira/browse/IGNITE-25044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov reassigned IGNITE-25044:
--------------------------------------
Assignee: Ivan Bessonov (was: Kirill Tkalenko)
> Test configuration compatibility with Apache Ignite 3.0
> -------------------------------------------------------
>
> Key: IGNITE-25044
> URL: https://issues.apache.org/jira/browse/IGNITE-25044
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
>
> We need a couple of tests:
> * Get a valid node configuration for Apache Ignite 3.0, try to run current
> version of code on it.
> * Same process, but instead of running a node on an old configuration, we
> instead initialize the cluster with "obsolete" script. This scenario is not
> really fail, but emulating Ignite version upgrade is problematic without
> having a proper compatibility framework.
> The "old" configurations should be retrieved from the real 3.0 installation,
> by calling corresponding REST/CLI commands.
> We should make sure that:
> * Every named list configuration is populated with some values.
> * Every instance of polymorphic configurations is tested. This is actually
> not possible to achieve withing a single configuration file, which means that
> we will have multiple tests for each scenario (probably a parameterized test).
> Obviously, these tests will be failing right now. We will have to disable
> them and fix all the incompatibilities. This must be done before Apache
> Ignite 3.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
