update-keyword-engine-lists

Update ALLOWED_KEYWORD_ALIASES in ClickHouseSqlUtils.java and ENGINE_TO_TABLE_TYPE in DatabaseMetaDataImpl.java from failing test output. Use when…

npx skills add https://github.com/clickhouse/clickhouse-java --skill update-keyword-engine-lists

Update keyword and engine lists from test failures

Files

Keywords: jdbc-v2/src/main/java/com/clickhouse/jdbc/internal/parser/javacc/ClickHouseSqlUtils.javainitAllowedKeywordAliases(), append after the last // Appended comment block.

Engines: jdbc-v2/src/main/java/com/clickhouse/jdbc/metadata/DatabaseMetaDataImpl.javaENGINE_TO_TABLE_TYPE static block, insert a new group before // Special.

Steps

  1. Parse the failing test message to extract the list of missing items.

  2. For keywords (StatementSQLTest failure — e.g. ["CURSOR", "DETERMINISTIC", ...]): Append a new dated comment + entries at the end of buildKeywordSet(...), after the last existing // Appended block:

    // Appended MM/DD/YYYY
    "KEYWORD1", "KEYWORD2", ...
    

    The previous entry must have a trailing comma. Keep alphabetical order within the new block.

  3. For engines (DatabaseMetaDataTest failure — e.g. [Paimon, PaimonAzure, ...]): Add a new named group before // Special in the static block:

    // <GroupName> (appended MM/DD/YYYY)
    map.put("Engine1", TableType.REMOTE_TABLE.getTypeName());
    

    Choose TableType by analogy:

    • External storage (S3/Azure/HDFS variants, lake formats) → REMOTE_TABLE
    • MergeTree family or local engines → TABLE

Output

After editing, output this git commit command:

git commit -m "jdbc-v2: update <keywords|engines|keywords and engines> in JDBC"

More skills from clickhouse

clickhouse-best-practices
clickhouse
28 ClickHouse best practices rules organized by schema design, query optimization, and data ingestion strategy. Covers three critical areas: primary key and data type selection (immutable design decisions), JOIN and query optimization, and insert batching with mutation avoidance Includes 28 rules prioritized by impact, with schema design and query optimization rules marked CRITICAL due to ClickHouse's columnar storage and sparse index mechanics Provides structured review procedures for...
official
clickhouse-js-node-coding
clickhouse
Write idiomatic application code with the ClickHouse Node.js client (`@clickhouse/client`). Use this skill whenever a user is *building* against the Node.js…
official
clickhousectl-cloud-deploy
clickhouse
Use when a user wants to deploy ClickHouse to the cloud, go to production, use ClickHouse Cloud, host a managed ClickHouse service, or migrate from a local…
official
clickstack-otel-collector
clickhouse
Use when a user wants to wire an OpenTelemetry collector into a Managed ClickStack service on ClickHouse Cloud, either by deploying a new local collector…
official
infra-clickhouse
clickhouse
Sets up and manages ClickHouse using the clickhousectl CLI — installs and runs a local ClickHouse server for development, and creates managed ClickHouse Cloud…
official
infra-postgres
clickhouse
Sets up and manages Postgres using the clickhousectl CLI — runs a local Docker-backed Postgres for development, and creates and operates managed ClickHouse…
official
clickhouse-best-practices
clickhouse
MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 31 rules that MUST be checked before providing recommendations. Always read…
official
setup
clickhouse
Guides users through setting up the ClickHouse MCP server connection bundled with this plugin. Use when the user first installs the plugin or has trouble…
official