temporalio / temporalio/temporal
SecondaryVisbilityStore validation failed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Expected Behavior
I want to migrate the visibility store from ES to Postgres using Dual Visibility Store feature. Expected behavior to be able to dual write to both ES and Postgres. Temporal config:
visibilityStore: es-visibility
secondaryVisibilityStore: pg-visibility
datastores:
pg-visibility:
SQL:
es-visibility:
elasticsearch:
Actual Behavior
Upon starting the server, I got the following error persistence config: cannot set secondaryVisibilityStore when visibilityStore is setting elasticsearch datastore
Steps to Reproduce the Problem
- Setup the config as above
- Start temporal server
Specifications
- Version: 1.22.3
- Platform: Linux
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 reproducing the Temporal 1.22.3 configuration on Linux and locate the validation that emits "cannot set secondaryVisibilityStore when visibilityStore is setting elasticsearch datastore." Trace the visibility-store configuration path and confirm that the ES primary and PostgreSQL secondary configuration can be accepted; done means the server starts with the shown dual-store setup and can dual-write.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, go, postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100