Package io.temporal.api.workflow.v1

Class WorkflowExecutionVersioningInfo.Builder

    • Method Detail

      • 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>

      • 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

      • 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 java.io.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:
        java.io.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.
 This field is first set after an execution completes its first workflow task on a versioned
 worker, and set again on completion of every subsequent workflow task.
 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.
 This field is first set after an execution completes its first workflow task on a versioned
 worker, and set again on completion of every subsequent workflow task.
 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.
 This field is first set after an execution completes its first workflow task on a versioned
 worker, and set again on completion of every subsequent workflow task.
 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.
 This field is first set after an execution completes its first workflow task on a versioned
 worker, and set again on completion of every subsequent workflow task.
 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.
 This field is first set after an execution completes its first workflow task on a versioned
 worker, and set again on completion of every subsequent workflow task.
 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

        public boolean hasDeployment()
         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.
        .temporal.api.deployment.v1.Deployment deployment = 2;
        Specified by:
        hasDeployment in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        Whether the deployment field is set.

      • getDeployment

        public Deployment getDeployment()
         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.
        .temporal.api.deployment.v1.Deployment deployment = 2;
        Specified by:
        getDeployment in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        The deployment.

      • setDeployment

        public WorkflowExecutionVersioningInfo.Builder setDeployment​(Deployment value)
         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.
        .temporal.api.deployment.v1.Deployment deployment = 2;

      • setDeployment

        public WorkflowExecutionVersioningInfo.Builder setDeployment​(Deployment.Builder builderForValue)
         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.
        .temporal.api.deployment.v1.Deployment deployment = 2;

      • mergeDeployment

        public WorkflowExecutionVersioningInfo.Builder mergeDeployment​(Deployment value)
         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.
        .temporal.api.deployment.v1.Deployment deployment = 2;

      • clearDeployment

        public WorkflowExecutionVersioningInfo.Builder clearDeployment()
         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.
        .temporal.api.deployment.v1.Deployment deployment = 2;

      • getDeploymentBuilder

        public Deployment.Builder getDeploymentBuilder()
         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.
        .temporal.api.deployment.v1.Deployment deployment = 2;

      • getDeploymentOrBuilder

        public DeploymentOrBuilder getDeploymentOrBuilder()
         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.
        .temporal.api.deployment.v1.Deployment deployment = 2;
        Specified by:
        getDeploymentOrBuilder 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 `deployment` when override is PINNED). An override
 can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
        .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 `deployment` when override is PINNED). An override
 can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
        .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 `deployment` when override is PINNED). An override
 can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
        .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 `deployment` when override is PINNED). An override
 can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
        .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 `deployment` when override is PINNED). An override
 can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
        .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 `deployment` when override is PINNED). An override
 can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
        .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 `deployment` when override is PINNED). An override
 can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
        .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 `deployment` when override is PINNED). An override
 can be set when starting a new execution, as well as afterwards by calling the
 `UpdateWorkflowExecutionOptions` API.
        .temporal.api.workflow.v1.VersioningOverride versioning_override = 3;
        Specified by:
        getVersioningOverrideOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder

      • hasDeploymentTransition

        public boolean hasDeploymentTransition()
         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.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4;
        Specified by:
        hasDeploymentTransition in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        Whether the deploymentTransition field is set.

      • getDeploymentTransition

        public DeploymentTransition getDeploymentTransition()
         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.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4;
        Specified by:
        getDeploymentTransition in interface WorkflowExecutionVersioningInfoOrBuilder
        Returns:
        The deploymentTransition.

      • setDeploymentTransition

        public WorkflowExecutionVersioningInfo.Builder setDeploymentTransition​(DeploymentTransition value)
         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.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4;

      • setDeploymentTransition

        public WorkflowExecutionVersioningInfo.Builder setDeploymentTransition​(DeploymentTransition.Builder builderForValue)
         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.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4;

      • mergeDeploymentTransition

        public WorkflowExecutionVersioningInfo.Builder mergeDeploymentTransition​(DeploymentTransition value)
         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.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4;

      • clearDeploymentTransition

        public WorkflowExecutionVersioningInfo.Builder clearDeploymentTransition()
         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.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4;

      • getDeploymentTransitionBuilder

        public DeploymentTransition.Builder getDeploymentTransitionBuilder()
         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.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4;

      • getDeploymentTransitionOrBuilder

        public DeploymentTransitionOrBuilder getDeploymentTransitionOrBuilder()
         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.
        .temporal.api.workflow.v1.DeploymentTransition deployment_transition = 4;
        Specified by:
        getDeploymentTransitionOrBuilder in interface WorkflowExecutionVersioningInfoOrBuilder