Search results

Server processes become orphaned — CLI loses track of running servers

Status: Open.

#89 In ClickHouse/clickhousectl;

· sdairs opened on Apr 4, 2026

Improve default text output of commands

Status: Open.

#87 In ClickHouse/clickhousectl;

· sdairs opened on Apr 4, 2026

Cleanly separate Local and Cloud CLI modules

Status: Open.

#86 In ClickHouse/clickhousectl;

· sdairs opened on Apr 4, 2026

Start a local server without switching default version

Status: Open.

#83 In ClickHouse/clickhousectl;

· sdairs opened on Apr 4, 2026

Support --json output for local commands

Status: Open.

#81 In ClickHouse/clickhousectl;

· sdairs opened on Apr 3, 2026

LLMs using cloud service commands in an org with existing services picks random services

Status: Open.

#58 In ClickHouse/clickhousectl;

· sdairs opened on Mar 26, 2026

Cloud API can return valid success JSON without inner result payload

Status: Open.

#50 In ClickHouse/clickhousectl;

· sdairs opened on Mar 16, 2026

add a way to show which cloud credential source was used

Status: Open.

#48 In ClickHouse/clickhousectl;

· sdairs opened on Mar 15, 2026

query_endpoint_create() accepts open_api but explicitly ignores it (let _ = open_api;) and always sends open_api_keys: None. This makes --open-api misleading and prevents configuring the endpoint as intended.

Status: Open.

#33 In ClickHouse/clickhousectl;

· sdairs opened on Mar 14, 2026

parse_org_private_endpoint_remove can return an OrganizationPatchPrivateEndpoint with id: None (e.g. when the user passes only description=... / region=...). The CLI help text implies the endpoint id is required for removals, and sending a remove patch without an id is likely invalid. Consider validating endpoint.id.is_some() before returning, and erroring with a clear message if it’s missing.

Status: Open.

#32 In ClickHouse/clickhousectl;

· sdairs opened on Mar 14, 2026

parse_service_endpoint_changes will happily accept the same protocol in both enable and disable (or multiple times), producing conflicting duplicate ServiceEndpointChange entries in the request. This makes the request ambiguous and can cause hard-to-debug API errors. Consider detecting conflicts/duplicates (e.g., by tracking seen protocols) and returning an error if a protocol is specified more than once or specified in both lists.

Status: Open.

#31 In ClickHouse/clickhousectl;

· sdairs opened on Mar 14, 2026

Support long running queries / polling

Status: Open.

#17 In ClickHouse/clickhousectl;

· sdairs opened on Mar 8, 2026