The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

A list of messages that carry the error details. There is a common set of message types for APIs to use.

System-generated ID of a task.

Name of the corresponding pod assigned by the orchestration engine. Also known as node_id.

A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).

In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:

• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)

Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.

Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.

Must be a valid serialized protocol buffer of the above specified type.

A list of artifact metadata ids.

The start time of the cron job.

The end time of the cron job.

Output. Unique experiment ID. Generated by API server.

Required input field. Unique experiment name provided by user.

Optional input field. Describes the purpose of the experiment.

Output. The time that the experiment was created.

Optional input field. Specify the namespace this experiment belongs to.

Output. Specifies whether this experiment is in archived or available state.

All predicates are AND-ed when this filter is applied.

Returns if KFP in multi-user mode

A list of experiments returned.

The number of experiments for the given query.

The token to list the next page of experiments.

Returned pipelines.

The total number of pipelines for the given query.

The token to list the next page of pipelines. This token can be used on the next ListPipelinesRequest.

Returned pipeline versions.

The token to list the next page of pipeline versions.

The total number of pipeline versions for the given query.

A list of recurring runs returned.

The total number of recurring runs for the given query.

The token to list the next page of recurring runs.

List of retrieved runs.

The total number of runs for the given query.

The token to list the next page of runs.

The start time of the periodic recurring run.

The end time of the periodic recurring run.

The time interval between the starting time of consecutive recurring runs.

Output. Unique pipeline ID. Generated by API server.

Required input field. Pipeline name provided by user.

Optional input field. A short description of the pipeline.

Output. Creation time of the pipeline.

Input. A namespace this pipeline belongs to. Causes error if user is not authorized to access the specified namespace. If not specified in CreatePipeline, default namespace is used.

In case any error happens retrieving a pipeline field, only pipeline ID, and the error message is returned. Client has the flexibility of choosing how to handle the error. This is especially useful during listing call.

ID of the parent run.

System-generated ID of a task.

User specified name of a task that is defined in [Pipeline.spec][].

Creation time of a task.

Starting time of a task.

Completion time of a task.

Execution information of a task.

Runtime state of a task.

Execution id of the corresponding entry in ML metadata store.

The error that occurred during task execution. Only populated when the task is in FAILED or CANCELED state.

Input artifacts of the task.

Output artifacts of the task.

ID of the parent task if the task is within a component scope. Empty if the task is at the root level.

A sequence of task statuses. This field keeps a record of state transitions.

Name of the corresponding pod assigned by the orchestration engine. Also known as node_id.

Sequence of dependen tasks.

The name of the job for the main container execution.

The name of the job for the pre-caching-check container execution. This job will be available if the Run.pipeline_spec specifies the pre_caching_check hook in the lifecycle events.

The names of the previously failed job for the main container executions. The list includes the all attempts in chronological order.

The names of the previously failed job for the pre-caching-check container executions. This job will be available if the Run.pipeline_spec specifies the pre_caching_check hook in the lifecycle events. The list includes the all attempts in chronological order.

Required input field. Unique ID of the parent pipeline.

Output. Unique pipeline version ID. Generated by API server.

Required input field. Pipeline version name provided by user.

Optional input field. Short description of the pipeline version.

Output. Creation time of the pipeline version.

Input. Required. The URL to the source of the pipeline version. This is required when creating the pipeine version through CreatePipelineVersion API.

Input. Optional. The URL to the code source of the pipeline version. The code is usually the Python definition of the pipeline and potentially related the component definitions. This allows users to trace back to how the pipeline YAML was created.

Output. The pipeline spec for the pipeline version.

In case any error happens retrieving a pipeline version field, only pipeline ID, pipeline version ID, and the error message are returned. Client has the flexibility of choosing how to handle the error. This is especially useful during List() calls.

Input. Required. Unique ID of the parent pipeline.

Input. Required. Unique ID of an existing pipeline version.

Key for the operation (first argument).

Integer.

Long integer.

String.

Timestamp values will be converted to Unix time (seconds since the epoch) prior to being used in a filtering operation.

Array values below are only meant to be used by the IN operator.

List of long integers.

List of strings.

Byte array of the artifact content.

Output. Unique run ID generated by API server.

Required input field. Recurring run name provided by user. Not unique.

Optional input field. Describes the purpose of the recurring run.

The ID of the pipeline version used for creating runs.

The pipeline spec.

Reference to a pipeline version containing pipeline_id and pipeline_version_id.

Runtime config of the pipeline.

Optional input field. Specifies which Kubernetes service account this recurring run uses.

Required input field. Specifies how many runs can be executed concurrently. Range [1-10].

Required input field. Specifies how a run is triggered. Support cron mode or periodic mode.

Output. The time this recurring run was created.

Output. The last time this recurring run was updated.

In case any error happens retrieving a recurring run field, only recurring run ID and the error message is returned. Client has the flexibility of choosing how to handle the error. This is especially useful during listing call.

Optional input field. Whether the recurring run should catch up if behind schedule. If true, the recurring run will only schedule the latest interval if behind schedule. If false, the recurring run will catch up on each past interval.

TODO (gkclat): consider removing this field if it can be obtained from the parent experiment. Output only. Namespace this recurring run belongs to. Derived from the parent experiment.

ID of the parent experiment this recurring run belongs to.

Input. ID of the parent experiment. The default experiment ID will be used if this is not specified.

Output. Unique run ID. Generated by API server.

Required input. Name provided by user, or auto generated if run is created by a recurring run.

Output. Specifies whether this run is in archived or available mode.

Optional input. Short description of the run.

ID of an existing pipeline version.

Pipeline spec.

Reference to a pipeline version containing pipeline_id and pipeline_version_id.

Required input. Runtime config of the run.

Optional input. Specifies which kubernetes service account is used.

Output. Creation time of the run.

Output. When this run is scheduled to start. This could be different from created_at. For example, if a run is from a backfilling job that was supposed to run 2 month ago, the created_at will be 2 month behind scheduled_at.

Output. Completion of the run.

Output. Runtime state of a run.

In case any error happens retrieving a run field, only run ID and the error message is returned. Client has the flexibility of choosing how to handle the error. This is especially useful during listing call.

Output. Runtime details of a run.

ID of the recurring run that triggered this run.

Output. A sequence of run statuses. This field keeps a record of state transitions.

Pipeline context ID of a run.

Pipeline run context ID of a run.

Runtime details of the tasks that belong to the run.

The runtime parameters of the Pipeline. The parameters will be used to replace the placeholders at runtime.

Update time of this state.

The state of a runtime instance.

The error that occurred during the state. May be set when the state is any of the non-final states (PENDING/RUNNING/CANCELING) or FAILED state. If the state is FAILED, the error here is final and not going to be retried. If the state is a non-final state, the error indicates that a system-error being retried.

URL of the pipeline version definition.

Path pattern of input data to be used during generation of visualizations. This is required when creating the pipeline through CreateVisualization API.

Variables to be used during generation of a visualization. This should be provided as a JSON string. This is required when creating the pipeline through CreateVisualization API.

Output. Generated visualization html.

In case any error happens when generating visualizations, only visualization ID and the error message are returned. Client has the flexibility of choosing how to handle the error.