amiirkhl/telecom-cdr-pipeline-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(pipeline): align delivery contracts and verification requirements

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-09-19 21:31:05 +03:30
parent 977f838eb2
commit bf439ab03c
10 changed files with 209 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
openspec/changes/telecom-cdr-pipeline/proposal.md
View File

@@ -30,3 +30,6 @@ Telecom network elements generate high-volume, heterogeneous Call Detail Records
- **Dependencies**: `confluent-kafka`, `clickhouse-connect`, `phonenumbers` (no web frameworks).
- **Infrastructure**: Kafka/Redpanda broker and ClickHouse database managed via Docker Compose.
- **Data Flow**: Network Element → HTTP API → Kafka (`cdr.raw`) → Worker → ClickHouse (`cdr_records`) / DLQ (`cdr.raw.dlq`).
## Delivery safety correction
Broker acknowledgement defines API acceptance. Explicit partition offsets advance only after acknowledged ClickHouse or DLQ storage. The assessment SQL omits identity from its replacement key; append cdr_id to prevent distinct events collapsing. Required-field HTTP rejection and direct Kafka fault injection resolve contradictory assessment examples. Existing assessment data is never reset automatically.