migrate freeze format to protobuf
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
> The freeze format's data container (Zlib-compressed JSON) is universally portable. However, maintaining its strict schema (currently defined via Python's Pydantic) across multiple languages requires manually redefining all structures, which is error-prone and maintenance-heavy. We should consider moving to Protobufs if our goal is to natively support feature ingestion in multiple languages like Go or Rust, as it provides automated code generation to enforce a single source of truth for the schema.
via @mike-hunhoff
Contributor guide
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.
Research direction
Start by locating the freeze format implementation and the Pydantic schema that currently defines its Zlib-compressed JSON data container. Review how freeze data is produced and consumed, including the intended Go and Rust ingestion paths. Done should mean a Protobuf schema and an agreed migration approach that preserves the freeze data model across languages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100