[
https://issues.apache.org/jira/browse/IGNITE-17416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-17416:
-------------------------------
Component/s: cli
> Support --cluster-url for dynamic config completions
> ----------------------------------------------------
>
> Key: IGNITE-17416
> URL: https://issues.apache.org/jira/browse/IGNITE-17416
> Project: Ignite
> Issue Type: Task
> Components: cli
> Reporter: Aleksandr
> Priority: Minor
> Labels: ignite-3, ignite-3-cli-tool
>
> IGNITE-17125 introduced the concept of dynamic completions in REPL mode. The
> main use case for them is the following:
> {code:bash}
> [node1] node config show --selector to <TAB>
> -> list of root config keys from node1 is shown as candidates for autocomplete
> {code}
> But the corner case is when a user is connected to the node1 but want's to
> see a config from node2:
> {code:bash}
> [node1] node config show --cluster-url=http://node2.localhost:10302
> --selector to <TAB>
> -> list of root config keys from node1 is shown as candidates for autocomplete
> {code}
> The URL for fetching the config will be taken from the global session and it
> will be the node1 URL. That might confuse a user if there are some changes
> between node1 and node2 config keys.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
