You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/06/21 13:54:00 UTC
[jira] [Updated] (IGNITE-19792) Support @Immutable logic for distributed configuration
[ https://issues.apache.org/jira/browse/IGNITE-19792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Puchkovskiy updated IGNITE-19792:
---------------------------------------
Description:
For distributed properties, the following scenario makes sense:
# Property value might be set on cluster init
# If it is provided, it overrides the default; otherwise, the default (set in the {{@Value}} annotation) is used
# Any attempt to modify the property value using a changer is rejected by a validator
{{@Immutable}} annotation is designed to trigger such behavior.
Now, the observed behavior is different: if a property is annotated as {{{}@Immutable{}}}, then, if a value is supplied during cluster initialization, the value is silently ignored, so it is impossible to configure such property to anything different from the default.
was:TBD
> Support @Immutable logic for distributed configuration
> ------------------------------------------------------
>
> Key: IGNITE-19792
> URL: https://issues.apache.org/jira/browse/IGNITE-19792
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> For distributed properties, the following scenario makes sense:
> # Property value might be set on cluster init
> # If it is provided, it overrides the default; otherwise, the default (set in the {{@Value}} annotation) is used
> # Any attempt to modify the property value using a changer is rejected by a validator
> {{@Immutable}} annotation is designed to trigger such behavior.
> Now, the observed behavior is different: if a property is annotated as {{{}@Immutable{}}}, then, if a value is supplied during cluster initialization, the value is silently ignored, so it is impossible to configure such property to anything different from the default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)