[jira] [Updated] (IGNITE-15916) "Any" listeners do not get notified for subclass-specific keys in Polymorphic Configurations
[ https://issues.apache.org/jira/browse/IGNITE-15916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-15916: - Ignite Flags: (was: Docs Required,Release Notes Required) > "Any" listeners do not get notified for subclass-specific keys in Polymorphic > Configurations > > > Key: IGNITE-15916 > URL: https://issues.apache.org/jira/browse/IGNITE-15916 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtcev >Priority: Minor > Labels: ignite-3 > > Polymorphic configuration allows having multiple inheritors of a base schema. > There also exists a feature that allows to add listeners for changes to "any" > configuration keys. This is implemented using a dummy configuration inside > the generated classes, where all such listeners get registered. However, this > does not work for Polymorphic schemas, because there's no way to know the > full set of configuration keys in advance, since the actual type of a > Polymorphic configuration instance is not known at the start. This leads to a > limitation: changes to subclass-specific keys are not propagated to "any" > listeners. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15916) "Any" listeners do not get notified for subclass-specific keys in Polymorphic Configurations
[ https://issues.apache.org/jira/browse/IGNITE-15916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-15916: --- Epic Link: IGNITE-14904 > "Any" listeners do not get notified for subclass-specific keys in Polymorphic > Configurations > > > Key: IGNITE-15916 > URL: https://issues.apache.org/jira/browse/IGNITE-15916 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtcev >Priority: Minor > Labels: ignite-3 > > Polymorphic configuration allows having multiple inheritors of a base schema. > There also exists a feature that allows to add listeners for changes to "any" > configuration keys. This is implemented using a dummy configuration inside > the generated classes, where all such listeners get registered. However, this > does not work for Polymorphic schemas, because there's no way to know the > full set of configuration keys in advance, since the actual type of a > Polymorphic configuration instance is not known at the start. This leads to a > limitation: changes to subclass-specific keys are not propagated to "any" > listeners. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15916) "Any" listeners do not get notified for subclass-specific keys in Polymorphic Configurations
[ https://issues.apache.org/jira/browse/IGNITE-15916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-15916: - Summary: "Any" listeners do not get notified for subclass-specific keys in Polymorphic Configurations (was: "Any" listeners do not get notified for all keys in Polymorphic Configurations) > "Any" listeners do not get notified for subclass-specific keys in Polymorphic > Configurations > > > Key: IGNITE-15916 > URL: https://issues.apache.org/jira/browse/IGNITE-15916 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtcev >Priority: Minor > Labels: ignite-3 > > Polymorphic configuration allows having multiple inheritors of a base schema. > There also exists a feature that allows to add listeners for changes to "any" > configuration keys. This is implemented using a dummy configuration inside > the generated classes, where all such listeners get registered. However, this > does not work for Polymorphic schemas, because there's no way to know the > full set of configuration keys in advance, since the actual type of a > Polymorphic configuration instance is not known at the start. This leads to a > limitation: changes to subclass-specific keys are not propagated to "any" > listeners. -- This message was sent by Atlassian Jira (v8.20.1#820001)
