snowplow / snowplow/dataflow-runner
Add jobflow name-based locking
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 19
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
This is a poor man's #17 - you use the EMR jobflow/cluster name to prevent multiple jobs from running at the same time. The jobflow will refuse to start if there is an existing running jobflow with the same name.
Contributor guide
No contributing guide indexed for this repository
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 issue #17 and the existing Amazon EMR jobflow handling in the repository. Implement name-based locking so a jobflow refuses to start when another running jobflow has the same name, and verify that this behavior is covered by the relevant existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, hadoop
- Domain
- cloud, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100