[
https://issues.apache.org/jira/browse/IGNITE-19294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-19294:
---------------------------------------
Description:
Сurrently, the configuration root can only be modified and extended in the
module where the configuration root is defined. Let's describe the situation.
Module *A* -> configuration root *Root1*
Module *B* depends on module {*}A{*}. In some cases, module *B* wants to extend
the *Root1* configuration with additional staff, but this is currently not
possible. This limitation looks artificial and there are cases when this
extension is necessary and in the current architecture we have to create a
separate root for each module, which, from the point of view of configuration
semantics, may look quite strange for the user.
> Union configuration root for several modules
> --------------------------------------------
>
> Key: IGNITE-19294
> URL: https://issues.apache.org/jira/browse/IGNITE-19294
> Project: Ignite
> Issue Type: New Feature
> Reporter: Mikhail Pochatkin
> Priority: Major
> Labels: ignite-3
>
> Сurrently, the configuration root can only be modified and extended in the
> module where the configuration root is defined. Let's describe the situation.
> Module *A* -> configuration root *Root1*
> Module *B* depends on module {*}A{*}. In some cases, module *B* wants to
> extend the *Root1* configuration with additional staff, but this is currently
> not possible. This limitation looks artificial and there are cases when this
> extension is necessary and in the current architecture we have to create a
> separate root for each module, which, from the point of view of configuration
> semantics, may look quite strange for the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
