[Feature]: Add composable SerDes transformation pipelines
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
首先阅读现有的 SerDes 和 FileSystemSerDes 实现及其配置 API,以了解当前的值编解码边界。通过所需的 RFC 定义阶段协议和组合语义,然后添加涵盖顺序、输入直通、null 和空值、格式错误的已识别 envelope 以及自定义值类型的测试,同时保持向后兼容性。
由索引模型根据 Issue 内容生成。
描述
What would you like?
Add a composable SerDes processing pipeline while preserving the existing object-to-string SerDes[T] API as the value-codec boundary.
Today, transformations such as filesystem offloading, compression, encryption, signing, or custom envelopes must each wrap and own another complete SerDes. This makes independent transformations difficult to reuse or reorder.
The proposed model is:
value -> root SerDes -> string stage -> string stage -> checkpoint
value <- root SerDes <- string stage <- string stage <- checkpoint
Possible Implementation
- Introduce a synchronous
SerDesStageprotocol whose serialize/deserialize methods accept and returnstrplusSerDesContext. - Add a
ComposableSerDesor composition helper that starts with one existingSerDes[T], applies stages in forward order during serialization, and reverses them during deserialization. - Require stages to emit a self-identifying/versioned format. During deserialization, a stage should:
- reverse valid input in its own format;
- raise
SerDesErrorfor malformed input that identifies itself as that stage; - return unrecognized input unchanged.
- Keep existing
SerDesimplementations and configuration APIs backward compatible. - Allow
FileSystemSerDesfunctionality to be exposed as a stage so callers can choose any root value codec and can place compression, encryption, or signing before or after storage as appropriate. - Add tests for stage order, pass-through of external invocation input, null/empty values, malformed recognized envelopes, and custom value types.
Is this a breaking change?
No.
Does this require an RFC?
Yes.
Additional Context
Python's current FileSystemSerDes already supports a configurable inner value SerDes. A pipeline would separate that value-codec responsibility from reusable string transformations instead of adding another nested-wrapper layer. A comparable Java design is being developed in aws/aws-durable-execution-sdk-java#648.
- 主要语言
- Python
- 星标
- 58
- 派生
- 32
- 平均合并
- 1 天 6 小时
- 30 天内合并 PR
- 80
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
aws/aws-durable-execution-sdk-python 的其他 Issue
-
enhancement needs-triage
难度 1/5 1-3 小时 新手友好度 72/100
aws/aws-durable-execution-sdk-python#927 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 82/100
aws/aws-durable-execution-sdk-python#875 ·
维护者通常 1 天内回复
-
enhancement
难度 1/5 1 小时以内 新手友好度 85/100
aws/aws-durable-execution-sdk-python#794 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 58/100
aws/aws-durable-execution-sdk-python#921 ·
维护者通常 1 天内回复
-
[Bug]: JS examples CI still invokes Jest after Vitest migration可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭bug needs-triage
难度 3/5 1-2 天 新手友好度 55/100
aws/aws-durable-execution-sdk-python#918 ·
维护者通常 1 天内回复
查看 aws/aws-durable-execution-sdk-python 的全部 Issue
相似的 Issue
-
physical
难度 2/5 1-3 小时 新手友好度 74/100
antonyrag/ragleap-core#1339 ·
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 83/100
AllenCell/SubCellSeg#5 ·
-
[🐛 Bug]: oidc_authverifier.py strips trailing slash causing "Invalid token: Invalid issuer" error未关闭
难度 2/5 1-3 小时 新手友好度 76/100
keephq/keep#6934 · 1 个 reaction ·
维护者通常 1 天内回复
-
bug game: 01008BA02525A000 ios
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
needs-triage
难度 1/5 1 小时以内 新手友好度 87/100
gke-labs/kube-agents#5501 ·
维护者通常 1 天内回复