ZIO streams: a typed error channel instead of Throwable?

未关闭
#121 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 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 内容生成。

描述

enhancement question

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 TableParserException for a bad row versus an IOException for 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,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

rchillyard/TableParser 的其他 Issue

查看 rchillyard/TableParser 的全部 Issue

相似的 Issue

更多 Scala Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。