ZIO streams: a typed error channel instead of Throwable?
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- scala
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.)
- 主要语言
- Scala
- 星标
- 11
- 派生
- 4
- 平均合并
- 2 小时 40 分钟
- 30 天内合并 PR
- 44
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
rchillyard/TableParser 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 91/100
rchillyard/TableParser#132 ·
维护者通常 1 天内回复
查看 rchillyard/TableParser 的全部 Issue
相似的 Issue
-
area:scripts priority:P2 status:backlog
难度 2/5 1-3 小时 新手友好度 78/100
KD5UJC-XYZ/scarab#1170 ·
维护者通常 1 天内回复
-
requires-triage
难度 2/5 1-3 小时 新手友好度 78/100
apache/datafusion-comet#7672 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
zio/zio-telemetry#1288 ·
维护者通常 1 天内回复
-
? - Needs Triage audit audit_4.3.0 audit_5.0.0
难度 2/5 1-3 小时 新手友好度 80/100
NVIDIA/cudf-spark#16965 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
valkey-io/valkey-glide#7745 ·
维护者通常 1 天内回复