temporalio / temporalio/temporal
Allow configurable time for history/visibility archiving
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Currently it's not possible to configure times when inline archiving of visibility and history data is triggered.
Archival can sometimes take a large number of resources, and it happens at unpredictable times at wf retention time. It would be helpful if users had the ability to configure a specific time or a time duration when archival should be performed (could be for example certain times when least production loads are expected).
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
No files, tests, or entry points are named. Start by locating the inline visibility and history archival implementation and its retention-time trigger, then review how archival configuration is loaded. Done should include a defined configuration for a scheduled time or duration, predictable archival behavior, and tests covering the trigger.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100