Deduplicate concurrent transforms schedule triggers
Open
.Backend
.Run Repro Bot
.Team/Gadget
Priority:P2
Transforms
Type:Bug
- Dominant language
- Clojure
- Stars
- 49.3k
- Forks
- 6.8k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 653
Description
When transform schedules run concurrently, triggers are not combined or deduplicated. This can lead to stale reads when there are dependencies between schedules, such as daily and weekly jobs running at the same time.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the transform schedule trigger orchestration and any concurrency-related tests; done means concurrent triggers are combined or deduplicated so dependent daily and weekly schedules do not produce stale reads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- backend, data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100