Handle updating cluster metadata search attributes info when using SQL DB #3861
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Register the pre-allocated custom search attributes when starting new instances of Temporal Server using SQL DB as visibility storage, or during the first start of the Server after upgrading to v1.20.
Why?
Support for advanced visibility using SQL DB: custom search attributes are pre-allocated and doing this automatically provides a more seamless experience to the user.
How did you test it?
Start new Server before changes, and then after. Logs show the search attributes being registered successfully:
Potential risks
No.
Is hotfix candidate?
No.