[
https://issues.apache.org/jira/browse/HDDS-14105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-14105:
------------------------------------
Fix Version/s: 2.2.0
Resolution: Implemented
Status: Resolved (was: Patch Available)
> Require ConfigGroup prefix to be present in Config keys
> -------------------------------------------------------
>
> Key: HDDS-14105
> URL: https://issues.apache.org/jira/browse/HDDS-14105
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Attila Doroszlai
> Assignee: Attila Doroszlai
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.2.0
>
>
> After HDDS-12424, {{ConfigGroup#prefix}} can now be included in
> {{Config#key}} to search by full config property name. HDDS-14030 added the
> prefix in all config keys to ensure consistent style. This change proposes
> to make the prefix mandatory so that we:
> - keep this consistent style in future
> - avoid typos
> For that, we need to remove support for inheriting configuration keys from
> ancestor classes. In theory this feature would help reuse, applying
> different prefixes to different subclasses of the same base one. However,
> this is currently used only in mock configuration classes, which exist for
> testing the configuration framework. I think descriptions, tags and maybe
> even default values would need to be different across subclasses, so it does
> not seem very practical. We can still inherit some implementation for reuse
> and apply the {{@Config}} annotation in the subclass.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
