You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 18, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 18, 2026. It is now read-only.
Sink shouldn't read tables from all databases on start-up #85
Noticed that the sink loads all tables from all schemas/databases on start-up, not just the specified database.
So in case of Clickhouse for example, if there is a table in an unrelated database with a valid schema that upstream library doesn't support, it throws an error:
{"severity":"ERROR","timestamp":"2025-03-25T16:14:59.243438056Z","logger":"sink-sql","message":"new db loader: load psql table: retrieving table and schema: clickhouse: unsupported column type \"AggregateFunction(argMin, Float64, Date)\"","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
Heads up: this repository is deprecated (see #133). The SQL sink was folded into the main substreams CLI as substreams sink postgres / substreams sink clickhouse, shipped in substreams v1.20.2. This repo gets security fixes only for one year, then goes read-only.
Leaving this open because the bug is real and the code still runs — it just lives at sink/sql/db_changes/ in streamingfast/substreams now. Any fix has to land there, so please refile or follow up upstream if you are still hitting it.
Activity
gowinder commentedon Aug 23, 2025
the same error
max-chechel-vc commentedon Sep 3, 2025
same issue here
GabrielCartier commentedon Aug 18, 2026
Heads up: this repository is deprecated (see #133). The SQL sink was folded into the main
substreamsCLI assubstreams sink postgres/substreams sink clickhouse, shipped in substreams v1.20.2. This repo gets security fixes only for one year, then goes read-only.Leaving this open because the bug is real and the code still runs — it just lives at
sink/sql/db_changes/in streamingfast/substreams now. Any fix has to land there, so please refile or follow up upstream if you are still hitting it.