HyperDX's own code runs against the edge, 17 of 17: parametric aggregates, LIKE's escape, arrays, and the words DuckDB keeps (T-496)

[chasers]

TL;DR: HyperDX's own code now runs against the edge, 17 of 17 steps. This PR fixes the 3 failures and 1 wrong answer that run found.

Tracker: T-496. Plan PL-66. Stacked on #356 (T-500).

How it was found

• Earlier layers were checked against SQL copied from HyperDX's source.
• This time HyperDX's code ran: its SQL generator, metadata reader and client wrapper (hyperdxio/hyperdx @ c42dda8), over the real @clickhouse/client.
• Target: a local smolquery node with 300 rows.

What the run found

Step	Result before	Cause
Search (11 forms), histogram, columns, table metadata	✅ passed
Field list, map keys, sidebar values	❌ syntax error	groupUniqArray(20)(x), groupUniqArrayArray(1000)(keys)
Search for user_id	❌ 0 rows of 75	LIKE lower('%user\_id%'): DuckDB's LIKE has no default escape character
Hand-written FROM default.otel_logs	❌ syntax error	default is a reserved word in DuckDB

What changed

• Rewrite: a parametric aggregate f(params)(args) becomes f(args, params). quantile is quantile_cont.
• Rewrite: a LIKE pattern holding a backslash gets ESCAPE '\'.
• Rewrite: a bare default. is quoted. isNull, isNotNull, any are renamed: they are the parser's own words.
• Macros: groupUniqArray, groupUniqArrayArray, groupArray, their -If forms, quantileIf, getSubcolumn, lowCardinalityKeys.
• Format: a list answers as Array(Nullable(T)). It was a String holding JSON. HyperDX reads keysArr as an array.

Watch out

• ⚠️ Behavior change: a list column in a result is now Array(...), in every format. Before it was JSON text typed String.
• ⚠️ An unaliased expression is named as DuckDB writes it (quantile_cont(...)), not as ClickHouse does. Only count() is renamed.
• ⚠️ Still not run: HyperDX's UI and API server. No container runs on the dev box.
• ⚠️ Still missing: WITH (expr) AS alias, JSONExtract(s, 'Map(...)'), toJSONString, CSV output.

How to repeat the run

• scripts/hyperdx-probe/probe.ts. Its header has the setup: clone HyperDX, npm install, run with tsx. Node only, no container.

Tests

• ✅ The three failing statements joined the fixture; the integration test asserts them.
• ✅ Rewrite, macro and array-format unit tests.
• ✅ Five chart configurations through HyperDX's chart builder answer (quantile by group, avg, max, filtered count and sum, count(DISTINCT)).

Checks

• ✅ mix precommit
• ✅ mix ci
• ✅ mix dialyzer

Review fixes

• ✅ x = ANY(SELECT ...) keeps its ANY. Only ClickHouse's aggregate any(x) is renamed.
• ✅ A list of structs answers as JSON text again, not as the text of an Elixir term.

🤖 Generated with Claude Code

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
37463487	Triggered	Generic Password	4eb5520	scripts/hyperdx-probe/probe.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}