Class WorkflowExecutionVersioningInfo.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<WorkflowExecutionVersioningInfo.Builder>
com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>
io.temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, WorkflowExecutionVersioningInfoOrBuilder, Cloneable
Enclosing class:
WorkflowExecutionVersioningInfo
public static final class WorkflowExecutionVersioningInfo.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder> implements WorkflowExecutionVersioningInfoOrBuilder
 Holds all the information about worker versioning for a particular workflow execution.
 Experimental. Versioning info is experimental and might change in the future.
Protobuf type temporal.api.workflow.v1.WorkflowExecutionVersioningInfo

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • clear

      public WorkflowExecutionVersioningInfo.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • getDefaultInstanceForType

      public WorkflowExecutionVersioningInfo getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public WorkflowExecutionVersioningInfo build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public WorkflowExecutionVersioningInfo buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • clone

      public WorkflowExecutionVersioningInfo.Builder clone()
      Specified by:
      clone in interface com.google.protobuf.Message.Builder
      Specified by:
      clone in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clone in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • setField

      public WorkflowExecutionVersioningInfo.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      setField in interface com.google.protobuf.Message.Builder
      Overrides:
      setField in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • clearField

      public WorkflowExecutionVersioningInfo.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
      Specified by:
      clearField in interface com.google.protobuf.Message.Builder
      Overrides:
      clearField in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • clearOneof

      public WorkflowExecutionVersioningInfo.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
      Specified by:
      clearOneof in interface com.google.protobuf.Message.Builder
      Overrides:
      clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • setRepeatedField

      public WorkflowExecutionVersioningInfo.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
      Specified by:
      setRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • addRepeatedField

      public WorkflowExecutionVersioningInfo.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      addRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • mergeFrom

      public WorkflowExecutionVersioningInfo.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<WorkflowExecutionVersioningInfo.Builder>

    • mergeFrom

      public WorkflowExecutionVersioningInfo.Builder mergeFrom(WorkflowExecutionVersioningInfo other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • mergeFrom

      public WorkflowExecutionVersioningInfo.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<WorkflowExecutionVersioningInfo.Builder>
      Throws:
      IOException

    • getBehaviorValue

      public int getBehaviorValue()
       Versioning behavior determines how the server should treat this execution when workers are
 upgraded. When present it means this workflow execution is versioned; UNSPECIFIED means
 unversioned. See the comments in `VersioningBehavior` enum for more info about different
 behaviors.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.
 
 Note that `behavior` is overridden by `versioning_override` if the latter is present.
      .temporal.api.enums.v1.VersioningBehavior behavior = 1;
      Specified by:
      getBehaviorValue in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The enum numeric value on the wire for behavior.

    • setBehaviorValue

      public WorkflowExecutionVersioningInfo.Builder setBehaviorValue(int value)
       Versioning behavior determines how the server should treat this execution when workers are
 upgraded. When present it means this workflow execution is versioned; UNSPECIFIED means
 unversioned. See the comments in `VersioningBehavior` enum for more info about different
 behaviors.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.
 
 Note that `behavior` is overridden by `versioning_override` if the latter is present.
      .temporal.api.enums.v1.VersioningBehavior behavior = 1;
      Parameters:
      value - The enum numeric value on the wire for behavior to set.
      Returns:
      This builder for chaining.

    • getBehavior

      public VersioningBehavior getBehavior()
       Versioning behavior determines how the server should treat this execution when workers are
 upgraded. When present it means this workflow execution is versioned; UNSPECIFIED means
 unversioned. See the comments in `VersioningBehavior` enum for more info about different
 behaviors.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.
 
 Note that `behavior` is overridden by `versioning_override` if the latter is present.
      .temporal.api.enums.v1.VersioningBehavior behavior = 1;
      Specified by:
      getBehavior in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The behavior.

    • setBehavior

      public WorkflowExecutionVersioningInfo.Builder setBehavior(VersioningBehavior value)
       Versioning behavior determines how the server should treat this execution when workers are
 upgraded. When present it means this workflow execution is versioned; UNSPECIFIED means
 unversioned. See the comments in `VersioningBehavior` enum for more info about different
 behaviors.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.
 
 Note that `behavior` is overridden by `versioning_override` if the latter is present.
      .temporal.api.enums.v1.VersioningBehavior behavior = 1;
      Parameters:
      value - The behavior to set.
      Returns:
      This builder for chaining.

    • clearBehavior

      public WorkflowExecutionVersioningInfo.Builder clearBehavior()
       Versioning behavior determines how the server should treat this execution when workers are
 upgraded. When present it means this workflow execution is versioned; UNSPECIFIED means
 unversioned. See the comments in `VersioningBehavior` enum for more info about different
 behaviors.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.
 
 Note that `behavior` is overridden by `versioning_override` if the latter is present.
      .temporal.api.enums.v1.VersioningBehavior behavior = 1;
      Returns:
      This builder for chaining.

    • hasDeployment

      @Deprecated public boolean hasDeployment()
      Deprecated.
      temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.deployment is deprecated. See temporal/api/workflow/v1/message.proto;l=162
       The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `deployment_version`.
      .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];
      Specified by:
      hasDeployment in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      Whether the deployment field is set.

    • getDeployment

      @Deprecated public Deployment getDeployment()
      Deprecated.
      temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.deployment is deprecated. See temporal/api/workflow/v1/message.proto;l=162
       The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `deployment_version`.
      .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];
      Specified by:
      getDeployment in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The deployment.

    • setDeployment

      @Deprecated public WorkflowExecutionVersioningInfo.Builder setDeployment(Deployment value)
      Deprecated.
       The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `deployment_version`.
      .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];

    • setDeployment

      @Deprecated public WorkflowExecutionVersioningInfo.Builder setDeployment(Deployment.Builder builderForValue)
      Deprecated.
       The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `deployment_version`.
      .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];

    • mergeDeployment

      @Deprecated public WorkflowExecutionVersioningInfo.Builder mergeDeployment(Deployment value)
      Deprecated.
       The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `deployment_version`.
      .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];

    • clearDeployment

      @Deprecated public WorkflowExecutionVersioningInfo.Builder clearDeployment()
      Deprecated.
       The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `deployment_version`.
      .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];

    • getDeploymentBuilder

      @Deprecated public Deployment.Builder getDeploymentBuilder()
      Deprecated.
       The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `deployment_version`.
      .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];

    • getDeploymentOrBuilder

      @Deprecated public DeploymentOrBuilder getDeploymentOrBuilder()
      Deprecated.
       The worker deployment that completed the last workflow task of this workflow execution. Must
 be present if `behavior` is set. Absent value means no workflow task is completed, or the
 last workflow task was completed by an unversioned worker. Unversioned workers may still send
 a deployment value which will be stored here, so the right way to check if an execution is
 versioned if an execution is versioned or not is via the `behavior` field.
 Note that `deployment` is overridden by `versioning_override` if the latter is present.
 Deprecated. Use `deployment_version`.
      .temporal.api.deployment.v1.Deployment deployment = 2 [deprecated = true];
      Specified by:
      getDeploymentOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder

    • getVersion

      @Deprecated public String getVersion()
      Deprecated.
      temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.version is deprecated. See temporal/api/workflow/v1/message.proto;l=164
       Deprecated. Use `deployment_version`.
      string version = 5 [deprecated = true];
      Specified by:
      getVersion in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The version.

    • getVersionBytes

      @Deprecated public com.google.protobuf.ByteString getVersionBytes()
      Deprecated.
      temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.version is deprecated. See temporal/api/workflow/v1/message.proto;l=164
       Deprecated. Use `deployment_version`.
      string version = 5 [deprecated = true];
      Specified by:
      getVersionBytes in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The bytes for version.

    • setVersion

      @Deprecated public WorkflowExecutionVersioningInfo.Builder setVersion(String value)
      Deprecated.
      temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.version is deprecated. See temporal/api/workflow/v1/message.proto;l=164
       Deprecated. Use `deployment_version`.
      string version = 5 [deprecated = true];
      Parameters:
      value - The version to set.
      Returns:
      This builder for chaining.

    • clearVersion

      @Deprecated public WorkflowExecutionVersioningInfo.Builder clearVersion()
      Deprecated.
      temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.version is deprecated. See temporal/api/workflow/v1/message.proto;l=164
       Deprecated. Use `deployment_version`.
      string version = 5 [deprecated = true];
      Returns:
      This builder for chaining.

    • setVersionBytes

      @Deprecated public WorkflowExecutionVersioningInfo.Builder setVersionBytes(com.google.protobuf.ByteString value)
      Deprecated.
      temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.version is deprecated. See temporal/api/workflow/v1/message.proto;l=164
       Deprecated. Use `deployment_version`.
      string version = 5 [deprecated = true];
      Parameters:
      value - The bytes for version to set.
      Returns:
      This builder for chaining.

    • hasDeploymentVersion

      public boolean hasDeploymentVersion()
       The Worker Deployment Version that completed the last workflow task of this workflow execution.
 An absent value means no workflow task is completed, or the workflow is unversioned.
 If present, and `behavior` is UNSPECIFIED, the last task of this workflow execution was completed
 by a worker that is not using versioning but _is_ passing Deployment Name and Build ID.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.

 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
      .temporal.api.deployment.v1.WorkerDeploymentVersion deployment_version = 7;
      Specified by:
      hasDeploymentVersion in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      Whether the deploymentVersion field is set.

    • getDeploymentVersion

      public WorkerDeploymentVersion getDeploymentVersion()
       The Worker Deployment Version that completed the last workflow task of this workflow execution.
 An absent value means no workflow task is completed, or the workflow is unversioned.
 If present, and `behavior` is UNSPECIFIED, the last task of this workflow execution was completed
 by a worker that is not using versioning but _is_ passing Deployment Name and Build ID.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.

 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
      .temporal.api.deployment.v1.WorkerDeploymentVersion deployment_version = 7;
      Specified by:
      getDeploymentVersion in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The deploymentVersion.

    • setDeploymentVersion

      public WorkflowExecutionVersioningInfo.Builder setDeploymentVersion(WorkerDeploymentVersion value)
       The Worker Deployment Version that completed the last workflow task of this workflow execution.
 An absent value means no workflow task is completed, or the workflow is unversioned.
 If present, and `behavior` is UNSPECIFIED, the last task of this workflow execution was completed
 by a worker that is not using versioning but _is_ passing Deployment Name and Build ID.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.

 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
      .temporal.api.deployment.v1.WorkerDeploymentVersion deployment_version = 7;

    • setDeploymentVersion

      public WorkflowExecutionVersioningInfo.Builder setDeploymentVersion(WorkerDeploymentVersion.Builder builderForValue)
       The Worker Deployment Version that completed the last workflow task of this workflow execution.
 An absent value means no workflow task is completed, or the workflow is unversioned.
 If present, and `behavior` is UNSPECIFIED, the last task of this workflow execution was completed
 by a worker that is not using versioning but _is_ passing Deployment Name and Build ID.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.

 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
      .temporal.api.deployment.v1.WorkerDeploymentVersion deployment_version = 7;

    • mergeDeploymentVersion

      public WorkflowExecutionVersioningInfo.Builder mergeDeploymentVersion(WorkerDeploymentVersion value)
       The Worker Deployment Version that completed the last workflow task of this workflow execution.
 An absent value means no workflow task is completed, or the workflow is unversioned.
 If present, and `behavior` is UNSPECIFIED, the last task of this workflow execution was completed
 by a worker that is not using versioning but _is_ passing Deployment Name and Build ID.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.

 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
      .temporal.api.deployment.v1.WorkerDeploymentVersion deployment_version = 7;

    • clearDeploymentVersion

      public WorkflowExecutionVersioningInfo.Builder clearDeploymentVersion()
       The Worker Deployment Version that completed the last workflow task of this workflow execution.
 An absent value means no workflow task is completed, or the workflow is unversioned.
 If present, and `behavior` is UNSPECIFIED, the last task of this workflow execution was completed
 by a worker that is not using versioning but _is_ passing Deployment Name and Build ID.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.

 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
      .temporal.api.deployment.v1.WorkerDeploymentVersion deployment_version = 7;

    • getDeploymentVersionBuilder

      public WorkerDeploymentVersion.Builder getDeploymentVersionBuilder()
       The Worker Deployment Version that completed the last workflow task of this workflow execution.
 An absent value means no workflow task is completed, or the workflow is unversioned.
 If present, and `behavior` is UNSPECIFIED, the last task of this workflow execution was completed
 by a worker that is not using versioning but _is_ passing Deployment Name and Build ID.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.

 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
      .temporal.api.deployment.v1.WorkerDeploymentVersion deployment_version = 7;

    • getDeploymentVersionOrBuilder

      public WorkerDeploymentVersionOrBuilder getDeploymentVersionOrBuilder()
       The Worker Deployment Version that completed the last workflow task of this workflow execution.
 An absent value means no workflow task is completed, or the workflow is unversioned.
 If present, and `behavior` is UNSPECIFIED, the last task of this workflow execution was completed
 by a worker that is not using versioning but _is_ passing Deployment Name and Build ID.

 Child workflows or CaN executions **inherit** their parent/previous run's effective Versioning 
 Behavior and Version (except when the new execution runs on a task queue not belonging to the 
 same deployment version as the parent/previous run's task queue). The first workflow task will
 be dispatched according to the inherited behavior (or to the current version of the task-queue's 
 deployment in the case of AutoUpgrade.) After completion of their first workflow task the 
 Deployment Version and Behavior of the execution will update according to configuration on the worker.

 Note that if `versioning_override.behavior` is PINNED then `versioning_override.pinned_version`
 will override this value.
      .temporal.api.deployment.v1.WorkerDeploymentVersion deployment_version = 7;
      Specified by:
      getDeploymentVersionOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder

    • hasVersioningOverride

      public boolean hasVersioningOverride()
       Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows, continue-as-new workflows,
 workflow retries, and cron workflows.
      .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;
      Specified by:
      hasVersioningOverride in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      Whether the versioningOverride field is set.

    • getVersioningOverride

      public VersioningOverride getVersioningOverride()
       Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows, continue-as-new workflows,
 workflow retries, and cron workflows.
      .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;
      Specified by:
      getVersioningOverride in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The versioningOverride.

    • setVersioningOverride

      public WorkflowExecutionVersioningInfo.Builder setVersioningOverride(VersioningOverride value)
       Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows, continue-as-new workflows,
 workflow retries, and cron workflows.
      .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;

    • setVersioningOverride

      public WorkflowExecutionVersioningInfo.Builder setVersioningOverride(VersioningOverride.Builder builderForValue)
       Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows, continue-as-new workflows,
 workflow retries, and cron workflows.
      .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;

    • mergeVersioningOverride

      public WorkflowExecutionVersioningInfo.Builder mergeVersioningOverride(VersioningOverride value)
       Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows, continue-as-new workflows,
 workflow retries, and cron workflows.
      .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;

    • clearVersioningOverride

      public WorkflowExecutionVersioningInfo.Builder clearVersioningOverride()
       Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows, continue-as-new workflows,
 workflow retries, and cron workflows.
      .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;

    • getVersioningOverrideBuilder

      public VersioningOverride.Builder getVersioningOverrideBuilder()
       Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows, continue-as-new workflows,
 workflow retries, and cron workflows.
      .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;

    • getVersioningOverrideOrBuilder

      public VersioningOverrideOrBuilder getVersioningOverrideOrBuilder()
       Present if user has set an execution-specific versioning override. This override takes
 precedence over SDK-sent `behavior` (and `version` when override is PINNED). An
 override can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
 Pinned overrides are automatically inherited by child workflows, continue-as-new workflows,
 workflow retries, and cron workflows.
      .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;
      Specified by:
      getVersioningOverrideOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder

    • hasDeploymentTransition

      @Deprecated public boolean hasDeploymentTransition()
      Deprecated.
      temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.deployment_transition is deprecated. See temporal/api/workflow/v1/message.proto;l=205
       When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
      .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];
      Specified by:
      hasDeploymentTransition in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      Whether the deploymentTransition field is set.

    • getDeploymentTransition

      @Deprecated public DeploymentTransition getDeploymentTransition()
      Deprecated.
      temporal.api.workflow.v1.WorkflowExecutionVersioningInfo.deployment_transition is deprecated. See temporal/api/workflow/v1/message.proto;l=205
       When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
      .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];
      Specified by:
      getDeploymentTransition in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The deploymentTransition.

    • setDeploymentTransition

      @Deprecated public WorkflowExecutionVersioningInfo.Builder setDeploymentTransition(DeploymentTransition value)
      Deprecated.
       When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
      .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];

    • setDeploymentTransition

      @Deprecated public WorkflowExecutionVersioningInfo.Builder setDeploymentTransition(DeploymentTransition.Builder builderForValue)
      Deprecated.
       When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
      .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];

    • mergeDeploymentTransition

      @Deprecated public WorkflowExecutionVersioningInfo.Builder mergeDeploymentTransition(DeploymentTransition value)
      Deprecated.
       When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
      .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];

    • clearDeploymentTransition

      @Deprecated public WorkflowExecutionVersioningInfo.Builder clearDeploymentTransition()
      Deprecated.
       When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
      .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];

    • getDeploymentTransitionBuilder

      @Deprecated public DeploymentTransition.Builder getDeploymentTransitionBuilder()
      Deprecated.
       When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
      .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];

    • getDeploymentTransitionOrBuilder

      @Deprecated public DeploymentTransitionOrBuilder getDeploymentTransitionOrBuilder()
      Deprecated.
       When present, indicates the workflow is transitioning to a different deployment. Can
 indicate one of the following transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current deployment if the task queue's current
 deployment is different from the workflow's deployment.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current deployment. As soon as a poller from
 that deployment is available to receive the task, the workflow will automatically start a
 transition to that deployment and continue execution there.
 A deployment transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target deployment, the
 transition completes and the workflow's `deployment` and `behavior` fields are updated per
 the worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new deployment.
 Deprecated. Use version_transition.
      .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4 [deprecated = true];
      Specified by:
      getDeploymentTransitionOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder

    • hasVersionTransition

      public boolean hasVersionTransition()
       When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `deployment_version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
      .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;
      Specified by:
      hasVersionTransition in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      Whether the versionTransition field is set.

    • getVersionTransition

      public DeploymentVersionTransition getVersionTransition()
       When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `deployment_version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
      .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;
      Specified by:
      getVersionTransition in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The versionTransition.

    • setVersionTransition

      public WorkflowExecutionVersioningInfo.Builder setVersionTransition(DeploymentVersionTransition value)
       When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `deployment_version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
      .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;

    • setVersionTransition

      public WorkflowExecutionVersioningInfo.Builder setVersionTransition(DeploymentVersionTransition.Builder builderForValue)
       When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `deployment_version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
      .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;

    • mergeVersionTransition

      public WorkflowExecutionVersioningInfo.Builder mergeVersionTransition(DeploymentVersionTransition value)
       When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `deployment_version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
      .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;

    • clearVersionTransition

      public WorkflowExecutionVersioningInfo.Builder clearVersionTransition()
       When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `deployment_version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
      .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;

    • getVersionTransitionBuilder

      public DeploymentVersionTransition.Builder getVersionTransitionBuilder()
       When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `deployment_version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
      .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;

    • getVersionTransitionOrBuilder

      public DeploymentVersionTransitionOrBuilder getVersionTransitionOrBuilder()
       When present, indicates the workflow is transitioning to a different deployment version
 (which may belong to the same deployment name or another). Can indicate one of the following
 transitions: unversioned -> versioned, versioned -> versioned
 on a different deployment version, or versioned -> unversioned.
 Not applicable to workflows with PINNED behavior.
 When a workflow with AUTO_UPGRADE behavior creates a new workflow task, it will automatically
 start a transition to the task queue's current version if the task queue's current version is
 different from the workflow's current deployment version.
 If the AUTO_UPGRADE workflow is stuck due to backlogged activity or workflow tasks, those
 tasks will be redirected to the task queue's current version. As soon as a poller from
 that deployment version is available to receive the task, the workflow will automatically
 start a transition to that version and continue execution there.
 A version transition can only exist while there is a pending or started workflow task.
 Once the pending workflow task completes on the transition's target version, the
 transition completes and the workflow's `behavior`, and `deployment_version` fields are updated per the
 worker's task completion response.
 Pending activities will not start new attempts during a transition. Once the transition is
 completed, pending activities will start their next attempt on the new version.
      .temporal.api.workflow.v1.DeploymentVersionTransition version_transition = 6;
      Specified by:
      getVersionTransitionOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder

    • getRevisionNumber

      public long getRevisionNumber()
       Monotonic counter reflecting the latest routing decision for this workflow execution.
 Used for staleness detection between history and matching when dispatching tasks to workers.
 Incremented when a workflow execution routes to a new deployment version, which happens
 when a worker of the new deployment version completes a workflow task.
 Note: Pinned tasks and sticky tasks send a value of 0 for this field since these tasks do not
 face the problem of inconsistent dispatching that arises from eventual consistency between
 task queues and their partitions.
      int64 revision_number = 8;
      Specified by:
      getRevisionNumber in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The revisionNumber.

    • setRevisionNumber

      public WorkflowExecutionVersioningInfo.Builder setRevisionNumber(long value)
       Monotonic counter reflecting the latest routing decision for this workflow execution.
 Used for staleness detection between history and matching when dispatching tasks to workers.
 Incremented when a workflow execution routes to a new deployment version, which happens
 when a worker of the new deployment version completes a workflow task.
 Note: Pinned tasks and sticky tasks send a value of 0 for this field since these tasks do not
 face the problem of inconsistent dispatching that arises from eventual consistency between
 task queues and their partitions.
      int64 revision_number = 8;
      Parameters:
      value - The revisionNumber to set.
      Returns:
      This builder for chaining.

    • clearRevisionNumber

      public WorkflowExecutionVersioningInfo.Builder clearRevisionNumber()
       Monotonic counter reflecting the latest routing decision for this workflow execution.
 Used for staleness detection between history and matching when dispatching tasks to workers.
 Incremented when a workflow execution routes to a new deployment version, which happens
 when a worker of the new deployment version completes a workflow task.
 Note: Pinned tasks and sticky tasks send a value of 0 for this field since these tasks do not
 face the problem of inconsistent dispatching that arises from eventual consistency between
 task queues and their partitions.
      int64 revision_number = 8;
      Returns:
      This builder for chaining.

    • getContinueAsNewInitialVersioningBehaviorValue

      public int getContinueAsNewInitialVersioningBehaviorValue()
       Experimental.
 If this workflow is the result of a continue-as-new, this field is set to the initial_versioning_behavior
 specified in that command.
 Only used for the initial task of this run and the initial task of any retries of this run.
 Not passed to children or to future continue-as-new.

 Note: In the first release of Upgrade-on-CaN, when the only ContinueAsNewVersioningBehavior was AutoUpgrade,
 a non-empty InheritedAutoUpgradeInfo meant that the workflow should start as AutoUpgrade. So for compatibility
 with ContinueAsNew history commands generated during that time, know that an UNSPECIFIED value here is equivalent
 to ContinueAsNewVersioningBehaviorAutoUpgrade if the behavior of the workflow is AutoUpgrade.
      .temporal.api.enums.v1.ContinueAsNewVersioningBehavior continue_as_new_initial_versioning_behavior = 9;
      Specified by:
      getContinueAsNewInitialVersioningBehaviorValue in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The enum numeric value on the wire for continueAsNewInitialVersioningBehavior.

    • setContinueAsNewInitialVersioningBehaviorValue

      public WorkflowExecutionVersioningInfo.Builder setContinueAsNewInitialVersioningBehaviorValue(int value)
       Experimental.
 If this workflow is the result of a continue-as-new, this field is set to the initial_versioning_behavior
 specified in that command.
 Only used for the initial task of this run and the initial task of any retries of this run.
 Not passed to children or to future continue-as-new.

 Note: In the first release of Upgrade-on-CaN, when the only ContinueAsNewVersioningBehavior was AutoUpgrade,
 a non-empty InheritedAutoUpgradeInfo meant that the workflow should start as AutoUpgrade. So for compatibility
 with ContinueAsNew history commands generated during that time, know that an UNSPECIFIED value here is equivalent
 to ContinueAsNewVersioningBehaviorAutoUpgrade if the behavior of the workflow is AutoUpgrade.
      .temporal.api.enums.v1.ContinueAsNewVersioningBehavior continue_as_new_initial_versioning_behavior = 9;
      Parameters:
      value - The enum numeric value on the wire for continueAsNewInitialVersioningBehavior to set.
      Returns:
      This builder for chaining.

    • getContinueAsNewInitialVersioningBehavior

      public ContinueAsNewVersioningBehavior getContinueAsNewInitialVersioningBehavior()
       Experimental.
 If this workflow is the result of a continue-as-new, this field is set to the initial_versioning_behavior
 specified in that command.
 Only used for the initial task of this run and the initial task of any retries of this run.
 Not passed to children or to future continue-as-new.

 Note: In the first release of Upgrade-on-CaN, when the only ContinueAsNewVersioningBehavior was AutoUpgrade,
 a non-empty InheritedAutoUpgradeInfo meant that the workflow should start as AutoUpgrade. So for compatibility
 with ContinueAsNew history commands generated during that time, know that an UNSPECIFIED value here is equivalent
 to ContinueAsNewVersioningBehaviorAutoUpgrade if the behavior of the workflow is AutoUpgrade.
      .temporal.api.enums.v1.ContinueAsNewVersioningBehavior continue_as_new_initial_versioning_behavior = 9;
      Specified by:
      getContinueAsNewInitialVersioningBehavior in interface WorkflowExecutionVersioningInfoOrBuilder
      Returns:
      The continueAsNewInitialVersioningBehavior.

    • setContinueAsNewInitialVersioningBehavior

      public WorkflowExecutionVersioningInfo.Builder setContinueAsNewInitialVersioningBehavior(ContinueAsNewVersioningBehavior value)
       Experimental.
 If this workflow is the result of a continue-as-new, this field is set to the initial_versioning_behavior
 specified in that command.
 Only used for the initial task of this run and the initial task of any retries of this run.
 Not passed to children or to future continue-as-new.

 Note: In the first release of Upgrade-on-CaN, when the only ContinueAsNewVersioningBehavior was AutoUpgrade,
 a non-empty InheritedAutoUpgradeInfo meant that the workflow should start as AutoUpgrade. So for compatibility
 with ContinueAsNew history commands generated during that time, know that an UNSPECIFIED value here is equivalent
 to ContinueAsNewVersioningBehaviorAutoUpgrade if the behavior of the workflow is AutoUpgrade.
      .temporal.api.enums.v1.ContinueAsNewVersioningBehavior continue_as_new_initial_versioning_behavior = 9;
      Parameters:
      value - The continueAsNewInitialVersioningBehavior to set.
      Returns:
      This builder for chaining.

    • clearContinueAsNewInitialVersioningBehavior

      public WorkflowExecutionVersioningInfo.Builder clearContinueAsNewInitialVersioningBehavior()
       Experimental.
 If this workflow is the result of a continue-as-new, this field is set to the initial_versioning_behavior
 specified in that command.
 Only used for the initial task of this run and the initial task of any retries of this run.
 Not passed to children or to future continue-as-new.

 Note: In the first release of Upgrade-on-CaN, when the only ContinueAsNewVersioningBehavior was AutoUpgrade,
 a non-empty InheritedAutoUpgradeInfo meant that the workflow should start as AutoUpgrade. So for compatibility
 with ContinueAsNew history commands generated during that time, know that an UNSPECIFIED value here is equivalent
 to ContinueAsNewVersioningBehaviorAutoUpgrade if the behavior of the workflow is AutoUpgrade.
      .temporal.api.enums.v1.ContinueAsNewVersioningBehavior continue_as_new_initial_versioning_behavior = 9;
      Returns:
      This builder for chaining.

    • setUnknownFields

      public final WorkflowExecutionVersioningInfo.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      setUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      setUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>

    • mergeUnknownFields

      public final WorkflowExecutionVersioningInfo.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      mergeUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<WorkflowExecutionVersioningInfo.Builder>