- 1.68.0 (latest)
- 1.67.1
- 1.66.0
- 1.65.0
- 1.63.0
- 1.62.0
- 1.60.0
- 1.59.0
- 1.58.0
- 1.57.0
- 1.56.0
- 1.55.0
- 1.54.1
- 1.53.0
- 1.52.0
- 1.51.0
- 1.50.0
- 1.49.0
- 1.48.0
- 1.47.0
- 1.46.0
- 1.45.0
- 1.44.0
- 1.43.0
- 1.39.0
- 1.38.1
- 1.37.0
- 1.36.4
- 1.35.0
- 1.34.0
- 1.33.1
- 1.32.0
- 1.31.1
- 1.30.1
- 1.29.0
- 1.28.1
- 1.27.1
- 1.26.1
- 1.25.0
- 1.24.1
- 1.23.0
- 1.22.1
- 1.21.0
- 1.20.0
- 1.19.1
- 1.18.3
- 1.17.1
- 1.16.1
- 1.15.1
- 1.14.0
- 1.13.1
- 1.12.1
- 1.11.0
- 1.10.0
- 1.9.0
- 1.8.1
- 1.7.1
- 1.6.2
- 1.5.0
- 1.4.3
- 1.3.0
- 1.2.0
- 1.1.1
- 1.0.1
- 0.9.0
- 0.8.0
- 0.7.1
- 0.6.0
- 0.5.1
- 0.4.0
- 0.3.1
ListExecutionsRequest(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Request message for MetadataService.ListExecutions.
Attributes |
|
---|---|
Name | Description |
parent |
str
Required. The MetadataStore whose Executions should be listed. Format: projects/{project}/locations/{location}/metadataStores/{metadatastore}
|
page_size |
int
The maximum number of Executions to return. The service may return fewer. Must be in range 1-1000, inclusive. Defaults to 100. |
page_token |
str
A page token, received from a previous MetadataService.ListExecutions call. Provide this to retrieve the subsequent page. When paginating, all other provided parameters must match the call that provided the page token. (Otherwise the request will fail with an INVALID_ARGUMENT error.) |
filter |
str
Filter specifying the boolean condition for the Executions to satisfy in order to be part of the result set. The syntax to define filter query is based on https://google.aip.dev/160. Following are the supported set of filters: - **Attribute filtering**: For example: display_name = "test" . Supported fields include:
name , display_name , state , schema_title ,
create_time , and update_time . Time fields, such
as create_time and update_time , require values
specified in RFC-3339 format. For example:
create_time = "2020-11-19T11:30:00-04:00" .
- **Metadata field**: To filter on metadata fields use
traversal operation as follows:
metadata. For example:
metadata.field_1.number_value = 10.0 In case the
field name contains special characters (such as colon),
one can embed it inside double quote. For example:
metadata."field:1".number_value = 10.0
- **Context based filtering**: To filter Executions based
on the contexts to which they belong use the function
operator with the full resource name:
in_context( . For example:
in_context("projects/
Each of the above supported filters can be combined together
using logical operators (AND & OR ). Maximum nested
expression depth allowed is 5.
For example:
display_name = "test" AND metadata.field1.bool_value = true .
|
order_by |
str
How the list of messages is ordered. Specify the values to order by and an ordering operation. The default sorting order is ascending. To specify descending order for a field, users append a " desc" suffix; for example: "foo desc, bar". Subfields are specified with a . character, such as
foo.bar. see https://google.aip.dev/132#ordering for more
details.
|