Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip visibility database validation if advanced visibility is enabled #1497

Merged

Conversation

alexshtin
Copy link
Member

@alexshtin alexshtin commented Apr 26, 2021

What changed?
Skip visibility database validation if advanced visibility is enabled.

Why?
If advanced visibility is enabled (system.advancedVisibilityWritingMode is on in dynamic config) there is no need to validate visibility database configuration because it is not used. This allows to remove visibility database configuration from static config in case if advanced visibility is enabled. Closes #1280.

How did you test it?
Run server locally with and without ES.

Potential risks
If visibility database is not configured and system.advancedVisibilityWritingMode is changed to off while server is running, it will lead to unpredictable behaviour.

Is hotfix candidate?
No.

@alexshtin alexshtin requested a review from a team April 26, 2021 23:58
temporal/server.go Outdated Show resolved Hide resolved
@alexshtin alexshtin force-pushed the feature/fix-visibility-config-validation branch from de811f2 to f7c27f9 Compare April 27, 2021 01:13
@alexshtin alexshtin enabled auto-merge (squash) April 27, 2021 01:15
@alexshtin alexshtin merged commit 6c23f02 into temporalio:master Apr 27, 2021
@alexshtin alexshtin deleted the feature/fix-visibility-config-validation branch April 27, 2021 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove unnecessary dependency on DB visibility config if ES is used
2 participants