Repository navigation
Async ingest: document the eventual-consistency contract + optional sync ack / ingest-lag signal #230
Description
Activity
🔗 Related PRs
#182 - refactor: full api --> ingest --> clickhouse --> dlq refactor [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 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!
Area: ingest — gap + docs · found via WaveHouse-Stats dogfooding
Expected: a way to know when an accepted event is queryable, or to opt into waiting for it.
Actual:
POST /v1/ingestreturns 200 after the NATS publish, not after the ClickHouse write (internal/api/ingest.go:153-187). A just-accepted event isn't immediately visible. There's no sync-ack mode and no exposed ingest-lag / queue-depth signal, so consumers can't distinguish "not yet flushed" from "genuinely missing."Impact (Stats): this is the reason the reconciler needs a settle window before declaring drift — and we're sizing that window blind.
Scope: at minimum, document the eventual-consistency contract before launch (cheap, important for anyone building on ingest). Larger follow-on: an optional synchronous ack mode and/or an exposed ingest-lag metric.
From
WAVEHOUSE-FEEDBACK.md(WaveHouse-Stats dogfooding); validated by code-read against0f8826con 2026-06-04.