supabase / mcp / 31419639030

97%

Build Type

push

github

Committed by web-flow

Commit Message

fix: select query_logs dialect via logsDialect (#357)

Adds an optional `logsDialect` (`'clickhouse' | 'bigquery'`) to
`DebuggingOperations` so each platform declares which SQL its logs
endpoint speaks. `query_logs` then picks its whole dialect-appropriate
description and `sql` param hint from a single lookup table, instead of
hardcoding ClickHouse copy — no environment-conditional prose the model
has to reason about. Defaults to `'clickhouse'` when unset, so existing
platform implementers are unaffected.

Implements [Matt's `logsDialect`
suggestion](https://supabase.slack.com/archives/C08N7894QTG/p1784660787397029?thread_ts=1784624411.491679&cid=C08N7894QTG)
raised in the #333 review.

**Why**: it lets `query_logs` roll out across every environment without
env-specific branching. Hosted stays ClickHouse; self-hosted/CLI can
keep its BigQuery-backed logs endpoint and declare `logsDialect:
'bigquery'`. This unblocks shipping the MCP server to self-hosted
(studio) regardless of whether it's on BigQuery or ClickHouse, rather
than holding the studio image back until self-hosted moves to
ClickHouse.

> [!NOTE]
> The comment sketched "reuse the `get_logs` description for `bigquery`"
— I instead give `query_logs` a proper BigQuery-dialect description,
since `get_logs` describes a `service` param while `query_logs` takes
`sql`. The BigQuery `sql` hint mirrors the canonical Logflare
self-hosted schema (`cross join unnest(metadata)`); worth confirming
when studio wires up the platform.

Refs AI-1046

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Coverage Stats

348 of 382 branches covered (91.1%)

Branch coverage included in aggregate %.

51 of 51 new or added lines in 2 files covered. (100.0%)

36 existing lines in 2 files now uncovered.

2945 of 3030 relevant lines covered (97.19%)

49.82 hits per line