CHASM Visibility for workflows#10498
Open
rodrigozhou wants to merge 1 commit into
Open
Conversation
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Introduce CHASM Visibility for workflows.
history.enableChasmVisibilityRatiofloat value between[0, 1]: partially enables CHASM Visibility for new workflows.0 < ratio < 1, custom search attributes and memo is duplicated in mutable state and CHASM Visibility. CHASM Visibility task is generated instead of theStart/Upsert/CloseVisibility tasks. CHASM Visibility becomes the source of truth for custom search attributes and memo (eg: forDescribeAPI`).ratio = 1, custom search attributes and memo are no longer stored in mutable state.Why?
CHASM Visibility to store custom search attributes and memo replacing the storage in mutable state.
How did you test it?
Potential risks