TLS to ClickHouse, and why a self-signed node fails
An https URL sets TLS and moves the default port, but only the platform trust store applies, so a custom CA has nowhere to go on this transport.
6 posts
Writing on ClickHouse
HTTP interface with system.* introspection, EXPLAIN pipelines and query-log monitoring. Where it stops: No foreign keys exist, so ER diagrams show structure without discovered relations.
Hiding an edit control that could only ever fail
A bare update statement answers not implemented on this engine, so no editable cell is offered, and the documented route reports zero rows changed.
ClickHouse diagrams show structure without relations
An empty edge list here is the engine answer, not an unfinished read: no engine, no table setting and no DDL declares a foreign key anywhere.
Monitoring ClickHouse from its own system tables
Every ClickHouse monitoring panel is a read of a catalog the server already maintains, with two boundaries: a setting that empties one panel, and a counter nobody publishes.
Connecting to ClickHouse over the HTTP interface
Port 8123 is the whole transport, the native port is never used, and a permission denial arrives as a 500, so failures are read by exception code.
Reading ClickHouse plans as JSON trees
The estimated plan is the only plan there is, because this engine never executes the statement to produce one, so nothing in the view was measured.