Keeper Client

[pufit]

Changelog category (leave one):

• New Feature

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Added native ClickHouse Keeper CLI Client.

Documentation entry for user-facing changes

• Documentation is written (mandatory for new features)

#46229

Example

./clickhouse-keeper-client localhost:2181 --connection-timeout 30 --session-timeout 30 --operation-timeout 30
Connected to ZooKeeper at [::1]:2181 with session_id 137
/ :) ls
keeper pufit foo bar
/ :) cd keeper
/keeper :) ls
api_version
/keeper :) cd api_version
/keeper/api_version :) ls

/keeper/api_version :) cd lolkek
Path /keeper/api_version/lolkek does not exists
/keeper/api_version :) cd ../../
/ :) ls
keeper pufit foo bar
/ :) get keeper/api_version
2

[antonio2368]

would be nice to have it as a standalone binary so maybe think early about minimizing included libs?
This is just a suggestion so feel free to do it in any way you think it's easiest for you.

[nikitamikhaylov]

@antonio2368 Initial idea was to include this client only to standalone keeper and bigger clickhouse binary

[antonio2368]

that also works

[nikitamikhaylov]

I'm thinking that it would be also nice and easy to support 4 letter commands. The output will be like this

:) ruok
imok
:) mntr
zk_version	v23.3.1.2537-testing-52bf836e03a6ba7cf2d654eaaf73231701abc3a2
zk_avg_latency	0
zk_max_latency	0
zk_min_latency	0
zk_packets_received	0
zk_packets_sent	0
zk_num_alive_connections	0
zk_outstanding_requests	0
zk_server_state	standalone
zk_znode_count	3
zk_watch_count	0
zk_ephemerals_count	0
zk_approximate_data_size	612
zk_key_arena_size	4096
zk_latest_snapshot_size	0
zk_open_file_descriptor_count	33
zk_max_file_descriptor_count	18446744073709551615
zk_followers	0
zk_synced_followers	0

[alexey-milovidov]

.

[robot-ch-test-poll2]

This is an automated comment for commit 362055c with description of existing statuses. It's updated for the latest CI running
The full report is available here
The overall status of the commit is 🟢 success

Check name	Description	Status
CI running	A meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR	🟢 success
Docs Check	Builds and tests the documentation	🟢 success
Mergeable Check	Checks if all other necessary checks are successful	🟢 success
Push to Dockerhub	The check for building and pushing the CI related docker images to docker hub	🟢 success
Style Check	Runs a set of checks to keep the code style clean. If some of tests failed, see the related log from the report	🟢 success

[nikitamikhaylov]

CC @alexey-milovidov Merging is blocked until the requested changes are addressed...