Repository navigation
SSE/live-query yields no events for tables populated by a ClickHouse MATERIALIZED VIEW (only ingest-API writes republish to NATS) #362
Description
Activity
🔗 Related PRs
#124 - chore(api)!: drop hub wildcard fan-out; SSE/WS use ?table= (closes
#100) [merged]
#174 - refactor(table names): handle unsafe table names [closed]
#182 - refactor: full api --> ingest --> clickhouse --> dlq refactor [closed]
#313 - feat(docs): view-transition polish, branded search + 404, chrome pass [closed]
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
- added a commit that references this issue
on Sep 26, 2026
Summary
GET /v1/stream?table=Tonly emits events for rows written viaPOST /v1/ingest(which publishes to NATSingest.<table>; the SSE hub subscribesingest.>). IfTis the target table of a ClickHouseMATERIALIZED VIEW— rows land inTvia the MV, not the ingest API — no NATS event is published and the stream is silently empty (no error).Why it surprised us
A natural WaveHouse pattern is: ingest raw rows into a base table, expose a derived/projection table via an MV (e.g. a column-masked
positions_public), and stream the projection to public clients. That projection never streams — the base table does, but not the MV target.(Distinct from the already-tracked row-filter drift in
applyStreamPolicy, which is about which columns/rows an event carries. This is about MV-written rows producing no event at all.)Repro
CREATE TABLE base (...),CREATE TABLE derived (...),CREATE MATERIALIZED VIEW mv TO derived AS SELECT ... FROM base.GET /v1/stream?table=derived(subscribe).POST /v1/ingest?table=basea row that the MV projects intoderived.derivedvia/v1/query, but thederivedstream receives nothing.Impact
Live dashboards built on derived/projection tables silently receive zero updates — easy to misdiagnose as a client/auth problem. We only found it by testing each surface.
Workaround
Stream the base (ingest-API-written) table directly and rely on the JWT column policy to mask columns per role.
Suggested
Found building the SCC 2026 tracker pilot against a self-hosted WaveHouse.