You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2025/03/10 07:50:00 UTC
[jira] [Updated] (IGNITE-24740) ClusterPerTestIntegrationTest does not support different startup configuration
[ https://issues.apache.org/jira/browse/IGNITE-24740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladislav Pyatkov updated IGNITE-24740:
---------------------------------------
Description:
h3. Motivation
The base class (_ClusterPerTestIntegrationTest_) is frequently used for integration tests where the configured class is required before scenario. Currently, the only way to define the startap configuration is to use getNodeBootstrapConfigTemplate, but this way defines a generic template that is applied to all nodes.
For example, it is impossible to determine node attributes for specific nodes in a cluster, IP ports, e.t.c.
Also need to check _ClusterPerClassIntegrationTest_, because likely the same issue is for this base class also.
h3. Definition of done
Provide a way to define different startup configurations for different nodes.
Prove that it is the easiest way to use this on the existing tests (for example, test for data zone filters, where the different node attributes are used).
was:
h3. Motivation
The base class (ClusterPerTestIntegrationTest) is frequently used for integration tests where the configured class is required before scenario. Currently, the only way to define the startap configuration is to use getNodeBootstrapConfigTemplate, but this way defines a generic template that is applied to all nodes.
For example, it is impossible to determine node attributes for specific nodes in a cluster, IP ports, e.t.c.
Also need to check ClusterPerClassIntegrationTest, because likely the same issue is for this base class also.
h3. Definition of done
Provide a way to define different startup configurations for different nodes.
Prove that it is the easiest way to use this on the existing tests (for example, test for data zone filters, where the different node attributes are used).
> ClusterPerTestIntegrationTest does not support different startup configuration
> ------------------------------------------------------------------------------
>
> Key: IGNITE-24740
> URL: https://issues.apache.org/jira/browse/IGNITE-24740
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> The base class (_ClusterPerTestIntegrationTest_) is frequently used for integration tests where the configured class is required before scenario. Currently, the only way to define the startap configuration is to use getNodeBootstrapConfigTemplate, but this way defines a generic template that is applied to all nodes.
> For example, it is impossible to determine node attributes for specific nodes in a cluster, IP ports, e.t.c.
> Also need to check _ClusterPerClassIntegrationTest_, because likely the same issue is for this base class also.
> h3. Definition of done
> Provide a way to define different startup configurations for different nodes.
> Prove that it is the easiest way to use this on the existing tests (for example, test for data zone filters, where the different node attributes are used).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)