temporalio / temporalio/temporal
Consider separating retention period from uniqueness guarantee period
Open
@paulnpdev is already working on this.
Since Jan 5, 2023.
API
difficulty: medium
enhancement
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
Currently, the uniqueness of a workflow is directly related to the retention period after a workflow is closed.
This forces users to make uncomfortable choices between the size of the DB and the uniqueness guarantee.
Describe the solution you'd like
Allow uniqueness guarantee to be larger than the retention period. It would mean removing all the workflow data from DB, but keeping a small record that would preclude duplicated workflow starts.
Describe alternatives you've considered
Keep the system as it is.
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.
Assessment
This issue has not been assessed yet.