TimelyDataflow / TimelyDataflow/differential-dataflow
Fuel tank for all differential operators (potentially)
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 211
- Avg merge
- 10h 42m
- Merged PRs (30d)
- 34
Description
As discussed with @frankmcsherry -- currently Join (and maybe a few others) have fuel tanks on how many keys get processed in one execution / round (unsure of best terminology here) and maybe we want to extend this to other operators (e.g. reduce) as well?
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 reading the existing fuel-tank behavior for Join and clarify what “keys processed in one execution / round” means. Compare that behavior with reduce and the other operators under consideration, then determine the desired scope and completion criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- data-engineering, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100