Get desktop application:
View/edit binary Protocol Buffers messages
Specifies the algorithm used to determine the number of worker processes to run at any given point in time, based on the amount of data left to process, the number of workers, and how quickly existing workers are processing data.
Used in:
The algorithm is unknown, or unspecified.
Disable autoscaling.
Increase worker count over time to reduce job execution time.
Settings for WorkerPool autoscaling.
Used in:
The algorithm to use for autoscaling.
The maximum number of workers to cap scaling at.
Metadata for a BigQuery connector used by the job.
Used in:
Table accessed in the connection.
Dataset accessed in the connection.
Project accessed in the connection.
Query used to access data in the connection.
Metadata for a Cloud Bigtable connector used by the job.
Used in:
ProjectId accessed in the connection.
InstanceId accessed in the connection.
TableId accessed in the connection.
Metadata for a Datastore connector used by the job.
Used in:
Namespace used in the connection.
ProjectId accessed in the connection.
Describes any options that have an effect on the debugging of pipelines.
Used in:
When true, enables the logging of the literal hot key to the user's Cloud Logging.
The default set of packages to be staged on a pool of workers.
Used in:
The default set of packages to stage is unknown, or unspecified.
Indicates that no packages should be staged at the worker unless explicitly specified by the job.
Stage packages typically useful to workers written in Java.
Stage packages typically useful to workers written in Python.
Describes the environment in which a Dataflow Job runs.
Used in:
The prefix of the resources the system should use for temporary storage. The system will append the suffix "/temp-{JOBNAME} to this resource prefix, where {JOBNAME} is the value of the job_name field. The resulting bucket and object prefix is used as the prefix of the resources used to store temporary data needed during the job execution. NOTE: This will override the value in taskrunner_settings. The supported resource type is: Google Cloud Storage: storage.googleapis.com/{bucket}/{object} bucket.storage.googleapis.com/{object}
The type of cluster manager API to use. If unknown or unspecified, the service will attempt to choose a reasonable default. This should be in the form of the API service name, e.g. "compute.googleapis.com".
The list of experiments to enable. This field should be used for SDK related experiments and not for service related experiments. The proper field for service related experiments is service_options.
The list of service options to enable. This field should be used for service related experiments only. These experiments, when graduating to GA, should be replaced by dedicated fields or become default (i.e. always on).
If set, contains the Cloud KMS key identifier used to encrypt data at rest, AKA a Customer Managed Encryption Key (CMEK). Format: projects/PROJECT_ID/locations/LOCATION/keyRings/KEY_RING/cryptoKeys/KEY
The worker pools. At least one "harness" worker pool must be specified in order for the job to have workers.
A description of the process that generated the request.
A structure describing which components and their versions of the service are required in order to run the job.
The dataset for the current project where various workflow related tables are stored. The supported resource type is: Google BigQuery: bigquery.googleapis.com/{dataset}
The Cloud Dataflow SDK pipeline options specified by the user. These options are passed through the service and are used to recreate the SDK pipeline options on the worker in a language agnostic and platform independent way.
Identity to run virtual machines as. Defaults to the default account.
Which Flexible Resource Scheduling mode to run in.
The Compute Engine region (https://cloud.google.com/compute/docs/regions-zones/regions-zones) in which worker processing should occur, e.g. "us-west1". Mutually exclusive with worker_zone. If neither worker_region nor worker_zone is specified, default to the control plane's region.
The Compute Engine zone (https://cloud.google.com/compute/docs/regions-zones/regions-zones) in which worker processing should occur, e.g. "us-west1-a". Mutually exclusive with worker_region. If neither worker_region nor worker_zone is specified, a zone in the control plane's region is chosen based on available capacity.
Output only. The shuffle mode used for the job.
Any debugging options to be supplied to the job.
A message describing the state of a particular execution stage.
Used in:
The name of the execution stage.
Executions stage states allow the same set of values as JobState.
The time at which the stage transitioned to this state.
Metadata for a File connector used by the job.
Used in:
File Pattern used to access files by the connector.
Specifies the resource to optimize for in Flexible Resource Scheduling.
Used in:
Run in the default mode.
Optimize for lower execution time.
Optimize for lower cost.
Defines a job to be run by the Cloud Dataflow service. Do not enter confidential information when you supply string values using the API. Fields stripped from source Job proto: - steps - pipeline_description - transform_name_mapping
Used in:
The unique ID of this job. This field is set by the Cloud Dataflow service when the Job is created, and is immutable for the life of the job.
The ID of the Cloud Platform project that the job belongs to.
The user-specified Cloud Dataflow job name. Only one Job with a given name can exist in a project within one region at any given time. Jobs in different regions can have the same name. If a caller attempts to create a Job with the same name as an already-existing Job, the attempt returns the existing Job. The name must match the regular expression `[a-z]([-a-z0-9]{0,1022}[a-z0-9])?`
The type of Cloud Dataflow job.
The environment for the job.
The Cloud Storage location where the steps are stored.
The current state of the job. Jobs are created in the `JOB_STATE_STOPPED` state unless otherwise specified. A job in the `JOB_STATE_RUNNING` state may asynchronously enter a terminal state. After a job has reached a terminal state, no further state updates may be made. This field may be mutated by the Cloud Dataflow service; callers cannot mutate it.
The timestamp associated with the current state.
The job's requested state. `UpdateJob` may be used to switch between the `JOB_STATE_STOPPED` and `JOB_STATE_RUNNING` states, by setting requested_state. `UpdateJob` may also be used to directly set a job's requested state to `JOB_STATE_CANCELLED` or `JOB_STATE_DONE`, irrevocably terminating the job if it has not already reached a terminal state.
Deprecated.
The timestamp when the job was initially created. Immutable and set by the Cloud Dataflow service.
If this job is an update of an existing job, this field is the job ID of the job it replaced. When sending a `CreateJobRequest`, you can update a job by specifying it here. The job named here is stopped, and its intermediate state is transferred to this job.
The client's unique identifier of the job, re-used across retried attempts. If this field is set, the service will ensure its uniqueness. The request to create a job will fail if the service has knowledge of a previously submitted job with the same client's ID and job name. The caller may use this field to ensure idempotence of job creation across retried attempts to create a job. By default, the field is empty and, in that case, the service ignores it.
If another job is an update of this job (and thus, this job is in `JOB_STATE_UPDATED`), this field contains the ID of that job.
A set of files the system should be aware of that are used for temporary storage. These temporary files will be removed on job completion. No duplicates are allowed. No file patterns are supported. The supported files are: Google Cloud Storage: storage.googleapis.com/{bucket}/{object} bucket.storage.googleapis.com/{object}
User-defined labels for this job. The labels map can contain no more than 64 entries. Entries of the labels map are UTF8 strings that comply with the following restrictions: * Keys must conform to regexp: [\p{Ll}\p{Lo}][\p{Ll}\p{Lo}\p{N}_-]{0,62} * Values must conform to regexp: [\p{Ll}\p{Lo}\p{N}_-]{0,63} * Both keys and values are additionally constrained to be <= 128 bytes in size.
The [regional endpoint] (https://cloud.google.com/dataflow/docs/concepts/regional-endpoints) that contains this job.
This field may be mutated by the Cloud Dataflow service; callers cannot mutate it.
This field is populated by the Dataflow service to support filtering jobs by the metadata values provided here. Populated for ListJobs and all GetJob views SUMMARY and higher.
The timestamp when the job was started (transitioned to JOB_STATE_PENDING). Flexible resource scheduling jobs are started with some delay after job creation, so start_time is unset before start and is updated when the job is started by the Cloud Dataflow service. For other jobs, start_time always equals to create_time and is immutable and set by the Cloud Dataflow service.
If this is specified, the job's initial state is populated from the given snapshot.
Reserved for future use. This field is set only in responses from the server; it is ignored if it is set in any requests.
The data within all Job events.
Used in:
The Job event payload.
Additional information about how a Cloud Dataflow job will be executed that isn't contained in the submitted job.
Used in:
A mapping from each stage to the information about that stage.
Contains information about how a particular [google.dataflow.v1beta3.Step][google.dataflow.v1beta3.Step] will be executed.
Used in:
The steps associated with the execution stage. Note that stages may have several steps, and that a given step might be run by more than one stage.
Metadata available primarily for filtering jobs. Will be included in the ListJob response and Job SUMMARY view.
Used in:
The SDK version used to run the job.
Identification of a Spanner source used in the Dataflow job.
Identification of a BigQuery source used in the Dataflow job.
Identification of a Cloud Bigtable source used in the Dataflow job.
Identification of a Pub/Sub source used in the Dataflow job.
Identification of a File source used in the Dataflow job.
Identification of a Datastore source used in the Dataflow job.
Describes the overall state of a [google.dataflow.v1beta3.Job][google.dataflow.v1beta3.Job].
Used in:
,The job's run state isn't specified.
`JOB_STATE_STOPPED` indicates that the job has not yet started to run.
`JOB_STATE_RUNNING` indicates that the job is currently running.
`JOB_STATE_DONE` indicates that the job has successfully completed. This is a terminal job state. This state may be set by the Cloud Dataflow service, as a transition from `JOB_STATE_RUNNING`. It may also be set via a Cloud Dataflow `UpdateJob` call, if the job has not yet reached a terminal state.
`JOB_STATE_FAILED` indicates that the job has failed. This is a terminal job state. This state may only be set by the Cloud Dataflow service, and only as a transition from `JOB_STATE_RUNNING`.
`JOB_STATE_CANCELLED` indicates that the job has been explicitly cancelled. This is a terminal job state. This state may only be set via a Cloud Dataflow `UpdateJob` call, and only if the job has not yet reached another terminal state.
`JOB_STATE_UPDATED` indicates that the job was successfully updated, meaning that this job was stopped and another job was started, inheriting state from this one. This is a terminal job state. This state may only be set by the Cloud Dataflow service, and only as a transition from `JOB_STATE_RUNNING`.
`JOB_STATE_DRAINING` indicates that the job is in the process of draining. A draining job has stopped pulling from its input sources and is processing any data that remains in-flight. This state may be set via a Cloud Dataflow `UpdateJob` call, but only as a transition from `JOB_STATE_RUNNING`. Jobs that are draining may only transition to `JOB_STATE_DRAINED`, `JOB_STATE_CANCELLED`, or `JOB_STATE_FAILED`.
`JOB_STATE_DRAINED` indicates that the job has been drained. A drained job terminated by stopping pulling from its input sources and processing any data that remained in-flight when draining was requested. This state is a terminal state, may only be set by the Cloud Dataflow service, and only as a transition from `JOB_STATE_DRAINING`.
`JOB_STATE_PENDING` indicates that the job has been created but is not yet running. Jobs that are pending may only transition to `JOB_STATE_RUNNING`, or `JOB_STATE_FAILED`.
`JOB_STATE_CANCELLING` indicates that the job has been explicitly cancelled and is in the process of stopping. Jobs that are cancelling may only transition to `JOB_STATE_CANCELLED` or `JOB_STATE_FAILED`.
`JOB_STATE_QUEUED` indicates that the job has been created but is being delayed until launch. Jobs that are queued may only transition to `JOB_STATE_PENDING` or `JOB_STATE_CANCELLED`.
`JOB_STATE_RESOURCE_CLEANING_UP` indicates that the batch job's associated resources are currently being cleaned up after a successful run. Currently, this is an opt-in feature, please reach out to Cloud support team if you are interested.
The CloudEvent raised when a Job status changes.
The data associated with the event.
Specifies the processing model used by a [google.dataflow.v1beta3.Job], which determines the way the Job is managed by the Cloud Dataflow service (how workers are scheduled, how inputs are sharded, etc).
Used in:
The type of the job is unspecified, or unknown.
A batch job with a well-defined end point: data is read, data is processed, data is written, and the job is done.
A continuously streaming job with no end: data is read, processed, and written continuously.
The packages that must be installed in order for a worker to run the steps of the Cloud Dataflow job that will be assigned to its worker pool. This is the mechanism by which the Cloud Dataflow SDK causes code to be loaded onto the workers. For example, the Cloud Dataflow Java SDK might use this to install jars containing the user's code and all of the various dependencies (libraries, data files, etc.) required in order for that code to run.
Used in:
The name of the package.
The resource to read the package from. The supported resource type is: Google Cloud Storage: storage.googleapis.com/{bucket} bucket.storage.googleapis.com/
Metadata for a Pub/Sub connector used by the job.
Used in:
Topic accessed in the connection.
Subscription used in the connection.
Defines an SDK harness container for executing Dataflow pipelines.
Used in:
A docker container image that resides in Google Container Registry.
If true, recommends the Dataflow service to use only one core per SDK container instance with this image. If false (or unset) recommends using more than one core per SDK container instance with this image for efficiency. Note that Dataflow service may choose to override this property if needed.
Environment ID for the Beam runner API proto Environment that corresponds to the current SDK Harness.
The set of capabilities enumerated in the above Environment proto. See also [beam_runner_api.proto](https://github.com/apache/beam/blob/master/model/pipeline/src/main/proto/org/apache/beam/model/pipeline/v1/beam_runner_api.proto)
The version of the SDK used to run the job.
Used in:
The version of the SDK used to run the job.
A readable string describing the version of the SDK.
The support status for this SDK version.
The support status of the SDK used to run the job.
Used in:
Cloud Dataflow is unaware of this version.
This is a known version of an SDK, and is supported.
A newer version of the SDK family exists, and an update is recommended.
This version of the SDK is deprecated and will eventually be unsupported.
Support for this SDK version has ended and it should no longer be used.
Specifies the shuffle mode used by a [google.dataflow.v1beta3.Job], which determines the approach data is shuffled during processing. More details in: https://cloud.google.com/dataflow/docs/guides/deploying-a-pipeline#dataflow-shuffle
Used in:
Shuffle mode information is not available.
Shuffle is done on the worker VMs.
Shuffle is done on the service side.
Metadata for a Spanner connector used by the job.
Used in:
ProjectId accessed in the connection.
InstanceId accessed in the connection.
DatabaseId accessed in the connection.
Specifies what happens to a resource when a Cloud Dataflow [google.dataflow.v1beta3.Job][google.dataflow.v1beta3.Job] has completed.
Used in:
The teardown policy isn't specified, or is unknown.
Always teardown the resource.
Teardown the resource on success. This is useful for debugging failures.
Never teardown the resource. This is useful for debugging and development.
Specifies how IP addresses should be allocated to the worker machines.
Used in:
The configuration is unknown, or unspecified.
Workers should have public IP addresses.
Workers should have private IP addresses.
Describes one particular pool of Cloud Dataflow workers to be instantiated by the Cloud Dataflow service in order to perform the computations required by a job. Note that a workflow job may use multiple pools, in order to match the various computational requirements of the various stages of the job.
Used in:
The kind of the worker pool; currently only `harness` and `shuffle` are supported.
Number of Google Compute Engine workers in this pool needed to execute the job. If zero or unspecified, the service will attempt to choose a reasonable default.
Packages to be installed on workers.
The default package set to install. This allows the service to select a default set of packages which are useful to worker harnesses written in a particular language.
Machine type (e.g. "n1-standard-1"). If empty or unspecified, the service will attempt to choose a reasonable default.
Sets the policy for determining when to turndown worker pool. Allowed values are: `TEARDOWN_ALWAYS`, `TEARDOWN_ON_SUCCESS`, and `TEARDOWN_NEVER`. `TEARDOWN_ALWAYS` means workers are always torn down regardless of whether the job succeeds. `TEARDOWN_ON_SUCCESS` means workers are torn down if the job succeeds. `TEARDOWN_NEVER` means the workers are never torn down. If the workers are not torn down by the service, they will continue to run and use Google Compute Engine VM resources in the user's project until they are explicitly terminated by the user. Because of this, Google recommends using the `TEARDOWN_ALWAYS` policy except for small, manually supervised test jobs. If unknown or unspecified, the service will attempt to choose a reasonable default.
Size of root disk for VMs, in GB. If zero or unspecified, the service will attempt to choose a reasonable default.
Type of root disk for VMs. If empty or unspecified, the service will attempt to choose a reasonable default.
Fully qualified source image for disks.
Zone to run the worker pools in. If empty or unspecified, the service will attempt to choose a reasonable default.
The action to take on host maintenance, as defined by the Google Compute Engine API.
Metadata to set on the Google Compute Engine VMs.
Settings for autoscaling of this WorkerPool.
Network to which VMs will be assigned. If empty or unspecified, the service will use the network "default".
Subnetwork to which VMs will be assigned, if desired. Expected to be of the form "regions/REGION/subnetworks/SUBNETWORK".
Required. Docker container image that executes the Cloud Dataflow worker harness, residing in Google Container Registry. Deprecated for the Fn API path. Use sdk_harness_container_images instead.
The number of threads per worker harness. If empty or unspecified, the service will choose a number of threads (according to the number of cores on the selected machine type for batch, or 1 by convention for streaming).
Configuration for VM IPs.
Set of SDK harness containers needed to execute this pipeline. This will only be set in the Fn API path. For non-cross-language pipelines this should have only one entry. Cross-language pipelines will have two or more entries.