Decouple algebird ops from scio-core
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Scala
- Stars
- 2.6k
- Forks
- 534
- Avg merge
- 6d 38m
- Merged PRs (30d)
- 7
Description
At some point i think it would be good to have a scio-algebird specific module. It might even ease up the migration for 2.13.
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 reviewing how the algebird operations are currently coupled to scio-core and how a separate scio-algebird module would affect the project. Check the Scala 2.13 migration context before defining the module boundary. Done means the separation is implemented and the migration path is demonstrably easier.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100