search

temporalio / docker-builds

Temporal service Docker images build
https://hub.docker.com/r/temporaliotest/auto-setup
MIT License
30 stars 59 forks source link

[Feature Request] Allow Visibility Store to use the same Temporal database name #215

Closed khuezy closed 5 months ago

khuezy commented 5 months ago

Is your feature request related to a problem? Please describe.

Hi, I want to use the same database name for my visibility store, but when the auto-setup script runs, it updates the curr_version of the schema_version table... when the temporal-sqs-tool runs for the visibility store, it sets the setup-schema -v 0.0 and will fail because the curr_version is greater than 0.0 and thus fail to create the executions_visibility table.

As a workaround, I had to manually run the visibility migration files via psql -f 1.0 -> 1.6

Describe the solution you'd like

Add a new column to track the visibility version instead of sharing the same column that the main temporal table uses.

Additional context

robholland commented 5 months ago

We're not going to support this because the tooling expects to be able to use schema_version, and as you've found out, it cannot do that if the database is shared.