clickhouse/agent-skills

clickhouse-js-node-troubleshooting

Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client).

View source
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

ClickHouse Node.js Client Troubleshooting

Reference: https://clickhouse.com/docs/integrations/javascript

⚠️ Node.js runtime only. This skill covers the @clickhouse/client package running in a Node.js runtime exclusively — including Next.js Node runtime API routes, React Server Components, Server Actions, and standard Node.js processes. Do not apply this skill to browser client components, Web Workers, Next.js Edge runtime, Cloudflare Workers, or any usage of @clickhouse/client-web. For browser/edge environments, the correct package is @clickhouse/client-web.

How to Use This Skill

  1. Identify the issue — match symptoms to the Issue Index below and read the corresponding reference file.
  2. Lead with the diagnosis — explain what's likely causing the issue before giving the fix.
  3. Note version constraints — flag if a fix requires a minimum client version and check it against what the user provided.
  4. Ask only what's missing — if the fix is version-dependent and you don't know their version, ask; otherwise help immediately.

Issue Index

Identify the user's issue from the list below and read the corresponding reference file for detailed troubleshooting steps.

IssueSymptomsReference file
Socket Hang-Up / ECONNRESETsocket hang up, ECONNRESET, intermittent connection drops, long-running queries timing outreference/socket-hangup.md
Data Type MismatchesLarge integers returned as strings, decimal precision loss, Date/DateTime insertion failures, CANNOT_PARSE_INPUT_ASSERTION_FAILED inserting a UUID into a UInt128 columnreference/data-types.md
Read-Only User ErrorsErrors when using response compression with readonly=1 usersreference/readonly-users.md
Proxy / Pathname URL ConfusionWrong database selected, requests failing behind a proxy with a path prefixreference/proxy-pathname.md
TLS / Certificate ErrorsTLS handshake failures, certificate verification issues, mutual TLS setupreference/tls.md
Compression Not WorkingGZIP compression not activating for requests or responsesreference/compression.md
Logging Not Showing AnythingNo log output, need custom logger integrationreference/logging.md
Query Parameters Not InterpolatedParameterized queries not working, SQL injection concernsreference/query-params.md
FORMAT Clause / `SHOW POLICIES` ErrorsSyntax error from a duplicate FORMAT, or SHOW [ROW] POLICIES failing even with a format providedreference/query-format-clause.md

Still Stuck?

from this repository

More skills

All skills
clickhouse
Official

clickhouse-best-practices

MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 31 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.

installs
1.7K
GitHub stars
549
Updated
Sep 29
clickhouse
Official

chdb-sql

- Use when the user wants to run SQL — especially analytical SQL — on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake) without setting up a server. Provides chDB — embedded ClickHouse SQL in Python with 1000+ functions, Session for stateful multi-step pipelines, parametrized queries, and cross-source joins via s3(), mysql(), postgresql(), iceberg(), deltaLake(), remoteSecure() table functions. TRIGGER when: user

installs
4
GitHub stars
549
Updated
Sep 29
clickhouse
Official

clickhouse-architecture-advisor

MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs. Complements clickhouse-best-practices with decision frameworks and explicit provenance labels.

installs
4
GitHub stars
549
Updated
Sep 29
clickhouse
Official

infra-clickhouse

Sets up and manages ClickHouse using the clickhousectl CLI — installs and runs a local ClickHouse server for development, and creates managed ClickHouse Cloud services for production (authentication, service creation, schema migration, application connection). Use when the user wants to build an application with ClickHouse, set up a local ClickHouse dev environment, create tables and start querying, deploy ClickHouse to production or ClickHouse Cloud, or migrate from a local setup to the cloud.

installs
4
GitHub stars
549
Updated
Sep 29