temporalio / temporalio/sdk-java
Register multiple activity names for an activity
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
In the event of a refactor wherein activity names are changed (prefix added, method name changed, etc) there is no clean way to migrate from one activity name to another --> if a worker picks up an activity with a name that is not registered with that worker it will throw an ApplicationFailure.
Describe the solution you'd like
I would like to have the ability to register multiple activity names for an activity - this way one could deploy the activity name change and then on the next deploy delete the previous activity name.
Ideally there would be a mechanism to mark one activity name as deprecated.
Thanks!
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
The issue does not name files, tests, or an entry point. Start by locating activity registration APIs in the Java SDK and review how activity names are currently mapped; done means supporting multiple names for one activity and defining how a deprecated name behaves during migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100