Ivan Bessonov created IGNITE-25043:
--------------------------------------
Summary: Support configuration rename
Key: IGNITE-25043
URL: https://issues.apache.org/jira/browse/IGNITE-25043
Project: Ignite
Issue Type: Improvement
Reporter: Ivan Bessonov
h3. Problem
Sometimes we make a typo and want to fix it, or we simply want to rename a
configuration by adding some suffix, like {{Bytes}} or {{{}Millis{}}}. We
should be able to do that in a compatible way.
h3. Solution, roughly
There are two opposite things happening here:
* When we read/parse configuration, we should make sure that *old* name is
still parsed correctly, being recognized as a proper configuration key
* When we save/show configuration, we should use *new* name. *Old* name should
be deleted from the storage at the same time, if we're talking about saving
configuration to the storage.
These points affect both REST/CLI and configuration storages.
TBD
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
