ZIO streams: a typed error channel instead of Throwable?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- scala
- Domain
- backend-api-design
Research direction
Read docs/code-review-2026.md item 5 and inspect ZIOTable.streamFile, the other stream methods, and the kafka-zio pipeline signatures. Decide whether to adopt a typed error channel and define its error types and conversions; done means the API direction is settled, with the minor release and release note implications recorded.
Written by the indexing model from the issue text.
Description
Context
The 2.1.0 plan (docs/code-review-2026.md, streaming, item 5) said: "Consider a typed error channel for zio (e.g. ZStream[Any, ParserException, Row]) rather than Throwable." This was never decided. ZIOTable.streamFile and the other stream methods still give ZStream[Any, Throwable, parser.Row], and the Kafka pipelines are ZPipeline[Producer, Throwable, X, RecordMetadata].
To decide
- A typed error channel lets callers handle parse failures differently from I/O failures. For example, a
TableParserExceptionfor a bad row versus anIOExceptionfor a missing file, perhaps as a small sealed error type. - It adds conversions wherever ZIO code meets
Throwable(zio-kafka, file I/O), and it changes the API of the zio and kafka-zio modules. - fs2 has no equivalent (its error channel is always
Throwable), so the two modules would differ.
If adopted, it changes the API, so it belongs in a minor release, with a release note.
Release
Assuming the PVP version scheme (#122): a point release (x.y.Z) must stay binary compatible, and a minor release (x.Y.0) may break compatibility, with a release note.
Minor release, breaking. It changes the signatures of ZIOTable's stream methods and the kafka-zio pipelines, which breaks both source and binary compatibility, so it needs a release note. (Under the old early-semver scheme, it would have needed 3.0.0.)
- Dominant language
- Scala
- Stars
- 11
- Forks
- 4
- Avg merge
- 2h 40m
- Merged PRs (30d)
- 44
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rchillyard/TableParser
-
Difficulty 1/5 1-3 hours Newbie friendliness 91/100
rchillyard/TableParser#132 ·
Maintainers usually reply within 1 day
All issues in rchillyard/TableParser
Similar issues
-
area:scripts priority:P2 status:backlog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
KD5UJC-XYZ/scarab#1170 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
zio/zio-telemetry#1288 ·
Maintainers usually reply within 1 day
-
? - Needs Triage audit audit_4.3.0 audit_5.0.0
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
NVIDIA/cudf-spark#16965 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
valkey-io/valkey-glide#7745 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day