bcgov / bcgov/Mines-Data-Platform
How do we reduce number of data factory triggers here? Cached data? Stored data?
- Dominant language
- HCL
- Stars
- 0
- Forks
- 1
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Feature #88
Description:
Acceptance Criteria:
Other Considerations:
**Definition of Ready:**
- [ ] The story is clearly written and explains Who needs What and Why.
- [ ] Acceptance criteria is clearly specified and understood by the team.
- [ ] The team has discussed and agreed upon how much story points /effort the story will require.
- [ ] There are no external dependencies preventing work on the story.
- [ ] All necessary design elements are completed and reviewed by the team.
- [ ] The technical approach has been reviewed, and any major technical risks or uncertainties have been addressed.
- [ ] The story size as small and efficient in size and can be done within a sprint
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading Feature #88 and locating the data factory trigger setup; the issue names no files, tests, or entry points. Clarify which triggers are in scope, whether cached or stored data is acceptable, and add acceptance criteria that define the expected reduction and how it will be verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100