temporalio / temporalio/temporal
Rename Visibility schema's version table to avoid conflict with Temporal schema
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 and Temporal Visibility schemas currently can't coexist in the same database because both utilize the same table name schema_version. This naming conflict causes versioning conflicts and blocks seamless schema upgrades.
Proposed Solution:
Rename the Visibility schema’s versioning table, e.g., from schema_version to something distinct such as visibility_version.
Benefits:
This would allow both schemas to coexist without conflicts, enabling smoother upgrades and coexistence of multiple schema versions.
Additional Context (Optional):
This suggestion arose from a discussion in https://community.temporal.io/t/allow-temporal-and-visibility-schemas-in-a-single-database-by-renaming-schema-version-table/17151.
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
Start by locating the Visibility schema's use of the shared schema_version table and the related schema upgrade paths; the issue does not name specific files or tests. Done means the Visibility version table has a distinct name such as visibility_version, while Temporal and Visibility schemas can coexist and upgrade without versioning conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100