[
https://issues.apache.org/jira/browse/IGNITE-24557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952022#comment-17952022
]
Ivan Bessonov commented on IGNITE-24557:
----------------------------------------
[~yuri_yudin] it works exactly as intended. I think we should properly document
the behavior of "update" command instead.
> CLI node config update doesn't rewrite the section, but adds it into the
> existing config
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-24557
> URL: https://issues.apache.org/jira/browse/IGNITE-24557
> Project: Ignite
> Issue Type: Bug
> Components: cli
> Reporter: Yury Yudin
> Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> I tried to rewrite ignite.storage.profiles section with completely new
> values, but the command adds additional section into the profiles list,
> instead of replacing it.
> {code}
> [ggnode1-ubuntu-new-2025-02-18]> node config show ignite.storage
> ...
> profiles=[
> {
> engine=aipersist
> name=default
> replacementMode=CLOCK
> size=40458666803
> }
> ]
> [ggnode1-ubuntu-new-2025-02-18]> node config update ignite.storage.profiles=[
> \{ "engine" : "rocksdb", "name" : "rocks" }]
> Node configuration updated. Restart the node to apply changes.
> [ggnode1-ubuntu-new-2025-02-18]> node config show ignite.storage
> ...
> profiles=[
> {
> engine=aipersist
> name=default
> replacementMode=CLOCK
> size=40458666803
> },
> {
> engine=rocksdb
> name=rocks
> size=268435456
> writeBufferSize=67108864
> }
> ]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
