You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2022/10/18 12:21:00 UTC

[jira] [Updated] (IGNITE-17516) Support fields with same name in different members of dynamic config hierarcny

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

Vyacheslav Koptilin updated IGNITE-17516:
-----------------------------------------
    Fix Version/s: 3.0.0-beta2
                       (was: 3.0.0-beta1)

> Support fields with same name in different members of dynamic config hierarcny
> ------------------------------------------------------------------------------
>
>                 Key: IGNITE-17516
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17516
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> In IGNITE-17497, an ability to have more than 2 levels of polymorphic configuration classes (base and instance) is introduced. This means that fields with same name might present on several levels of hierarchy. Currently, it's not clear whether it's supported (as we have 2 levels, more than one) or forbidden.



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