You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksandr (Jira)" <ji...@apache.org> on 2022/11/14 09:39:00 UTC
[jira] [Created] (IGNITE-18148) Dynamic completions improvements
Aleksandr created IGNITE-18148:
----------------------------------
Summary: Dynamic completions improvements
Key: IGNITE-18148
URL: https://issues.apache.org/jira/browse/IGNITE-18148
Project: Ignite
Issue Type: Task
Components: rest
Reporter: Aleksandr
The current state of DynamicCompletions is a first iteration that might be improved. Also, some inconsistency might be observed for the following case:
- user sees the list of completions on `node config show`
- user adds one more configuration key, say key1.key2
- `node config show` does not display key1.key2.
It happens because the list of keys is calculated once on the first call. After the cached value is used. This is done just for simplicity and is expected to be improved.
The goal of this ticket is to develop an API for operating with cluster state from CLI perspective. The actual set of configuration keys, the actual map of node names and urls, etc.
The API should be generic and flexible. In the future, we might use some notification mechanism and this API should be extended by this easily.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)