temporalio / temporalio/temporal
Allow Configurable Prefixes for Temporal Schema Table Names
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Current Situation:
Temporal Server currently uses fixed table names, causing naming conflicts when multiple Temporal deployments or environments share a single database schema.
Proposed Solution:
Add an optional configuration setting to allow specifying a custom prefix for all Temporal tables during schema initialization.
Example: -- add_prefix "dev_" results in tables like "dev_executions", "dev_schema_version". Temporal Server should support these prefixed tables, ensuring all existing operations remain functional.
Benefits:
Prevent naming conflicts in shared schemas.
Easier management of multiple environments.
Improved flexibility and compliance with naming conventions.
Thank you!
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 or tests are named in the issue. Start by locating schema initialization and the code that references Temporal table names, then trace how a configurable prefix would flow through existing operations; done means prefixed tables initialize successfully and all existing database operations remain functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100