You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support client-side specification of consistency for DescribeWorkflowExecution and GetWorkflowExecutionHistory (#6789)
* feat(frontend): Support client requested consistency levels
Some clients require strong consistency for reads on the DescribeWorkflowExecution and GetWorkflowExecutionHistory rpcs, and are willing to accept the latency trade-off.
This adds internal support for endpoints to define a consistency level.
* Add tests and remove QueryWorkflowStrongConsistency from configuration
* make pr
{{$domainIDAPIs := list "RecordActivityTaskHeartbeat" "RespondActivityTaskCanceled" "RespondActivityTaskCompleted" "RespondActivityTaskFailed" "RespondDecisionTaskCompleted" "RespondDecisionTaskFailed" "RespondQueryTaskCompleted"}}
17
17
{{$queryTaskTokenAPIs := list "RespondQueryTaskCompleted"}}
18
-
{{$specialCaseAPIs := list "QueryWorkflow"}}
18
+
{{$readAPIsWithStrongConsistency := list "QueryWorkflow" "DescribeWorkflowExecution" "GetWorkflowExecutionHistory"}}
19
19
20
20
type (
21
21
// ClusterRedirectionHandlerImpl is simple wrapper over frontend service, doing redirection based on policy for global domains not being active in current cluster
0 commit comments