- 1.35.0 (latest)
- 1.34.0
- 1.33.0
- 1.32.1
- 1.31.0
- 1.30.0
- 1.26.0
- 1.23.0
- 1.22.0
- 1.21.0
- 1.20.0
- 1.19.0
- 1.18.0
- 1.17.0
- 1.16.0
- 1.15.0
- 1.14.0
- 1.13.1
- 1.12.0
- 1.11.0
- 1.10.0
- 1.9.0
- 1.8.0
- 1.7.0
- 1.6.0
- 1.5.0
- 1.4.0
- 1.3.0
- 1.2.0
- 1.1.0
- 1.0.0
- 0.39.0
- 0.38.0
- 0.37.1
- 0.32.0
- 0.31.0
- 0.30.0
- 0.29.0
- 0.28.0
- 0.27.0
- 0.26.2
- 0.25.0
- 0.24.0
- 0.23.0
- 0.22.0
- 0.21.0
- 0.20.0
- 0.19.0
- 0.18.0
- 0.17.0
- 0.16.0
- 0.15.0
- 0.13.0
- 0.12.0
- 0.11.1
- 0.10.0
Reference documentation and code samples for the Google Cloud Ai Platform V1 Client class ListSchedulesRequest.
Request message for ScheduleService.ListSchedules .
Generated from protobuf message google.cloud.aiplatform.v1.ListSchedulesRequest
Namespace
Google \ Cloud \ AIPlatform \ V1Methods
__construct
Constructor.
data
array
Optional. Data for populating the Message object.
↳ parent
string
Required. The resource name of the Location to list the Schedules from. Format: projects/{project}/locations/{location}
↳ filter
string
Lists the Schedules that match the filter expression. The following fields are supported: * display_name
: Supports =
, !=
comparisons, and :
wildcard. * state
: Supports =
and !=
comparisons. * request
: Supports existence of the <request_type> check. (e.g. create_pipeline_job_request:*
--> Schedule has create_pipeline_job_request). * create_time
: Supports =
, !=
, <
, >
, <=
, and >=
comparisons. Values must be in RFC 3339 format. * start_time
: Supports =
, !=
, <
, >
, <=
, and >=
comparisons. Values must be in RFC 3339 format. * end_time
: Supports =
, !=
, <
, >
, <=
, >=
comparisons and :*
existence check. Values must be in RFC 3339 format. * next_run_time
: Supports =
, !=
, <
, >
, <=
, and >=
comparisons. Values must be in RFC 3339 format. Filter expressions can be combined together using logical operators ( NOT
, AND
& OR
). The syntax to define filter expression is based on https://google.aip.dev/160
. Examples: * state="ACTIVE" AND display_name:"my_schedule_*"
* NOT display_name="my_schedule"
* create_time>"2021-05-18T00:00:00Z"
* end_time>"2021-05-18T00:00:00Z" OR NOT end_time:*
* create_pipeline_job_request:*
↳ page_size
int
The standard list page size. Default to 100 if not specified.
↳ page_token
string
The standard list page token. Typically obtained via ListSchedulesResponse.next_page_token of the previous ScheduleService.ListSchedules call.
↳ order_by
string
A comma-separated list of fields to order by. The default sort order is in ascending order. Use "desc" after a field name for descending. You can have multiple order_by fields provided. For example, using "create_time desc, end_time" will order results by create time in descending order, and if there are multiple schedules having the same create time, order them by the end time in ascending order. If order_by is not specified, it will order by default with create_time in descending order. Supported fields: * create_time
* start_time
* end_time
* next_run_time
getParent
Required. The resource name of the Location to list the Schedules from.
Format: projects/{project}/locations/{location}
string
setParent
Required. The resource name of the Location to list the Schedules from.
Format: projects/{project}/locations/{location}
var
string
$this
getFilter
Lists the Schedules that match the filter expression. The following fields are supported:
-
display_name
: Supports=
,!=
comparisons, and:
wildcard. -
state
: Supports=
and!=
comparisons. -
request
: Supports existence of the <request_type> check. (e.g.create_pipeline_job_request:*
--> Schedule has create_pipeline_job_request). -
create_time
: Supports=
,!=
,<
,>
,<=
, and>=
comparisons. Values must be in RFC 3339 format. -
start_time
: Supports=
,!=
,<
,>
,<=
, and>=
comparisons. Values must be in RFC 3339 format. -
end_time
: Supports=
,!=
,<
,>
,<=
,>=
comparisons and:*
existence check. Values must be in RFC 3339 format. -
next_run_time
: Supports=
,!=
,<
,>
,<=
, and>=
comparisons. Values must be in RFC 3339 format. Filter expressions can be combined together using logical operators (NOT
,AND
&OR
). The syntax to define filter expression is based on https://google.aip.dev/160 . Examples: -
state="ACTIVE" AND display_name:"my_schedule_*"
-
NOT display_name="my_schedule"
-
create_time>"2021-05-18T00:00:00Z"
-
end_time>"2021-05-18T00:00:00Z" OR NOT end_time:*
-
create_pipeline_job_request:*
string
setFilter
Lists the Schedules that match the filter expression. The following fields are supported:
-
display_name
: Supports=
,!=
comparisons, and:
wildcard. -
state
: Supports=
and!=
comparisons. -
request
: Supports existence of the <request_type> check. (e.g.create_pipeline_job_request:*
--> Schedule has create_pipeline_job_request). -
create_time
: Supports=
,!=
,<
,>
,<=
, and>=
comparisons. Values must be in RFC 3339 format. -
start_time
: Supports=
,!=
,<
,>
,<=
, and>=
comparisons. Values must be in RFC 3339 format. -
end_time
: Supports=
,!=
,<
,>
,<=
,>=
comparisons and:*
existence check. Values must be in RFC 3339 format. -
next_run_time
: Supports=
,!=
,<
,>
,<=
, and>=
comparisons. Values must be in RFC 3339 format. Filter expressions can be combined together using logical operators (NOT
,AND
&OR
). The syntax to define filter expression is based on https://google.aip.dev/160 . Examples: -
state="ACTIVE" AND display_name:"my_schedule_*"
-
NOT display_name="my_schedule"
-
create_time>"2021-05-18T00:00:00Z"
-
end_time>"2021-05-18T00:00:00Z" OR NOT end_time:*
-
create_pipeline_job_request:*
var
string
$this
getPageSize
The standard list page size.
Default to 100 if not specified.
int
setPageSize
The standard list page size.
Default to 100 if not specified.
var
int
$this
getPageToken
The standard list page token.
Typically obtained via ListSchedulesResponse.next_page_token of the previous ScheduleService.ListSchedules call.
string
setPageToken
The standard list page token.
Typically obtained via ListSchedulesResponse.next_page_token of the previous ScheduleService.ListSchedules call.
var
string
$this
getOrderBy
A comma-separated list of fields to order by. The default sort order is in ascending order. Use "desc" after a field name for descending. You can have multiple order_by fields provided.
For example, using "create_time desc, end_time" will order results by create time in descending order, and if there are multiple schedules having the same create time, order them by the end time in ascending order. If order_by is not specified, it will order by default with create_time in descending order. Supported fields:
-
create_time
-
start_time
-
end_time
-
next_run_time
string
setOrderBy
A comma-separated list of fields to order by. The default sort order is in ascending order. Use "desc" after a field name for descending. You can have multiple order_by fields provided.
For example, using "create_time desc, end_time" will order results by create time in descending order, and if there are multiple schedules having the same create time, order them by the end time in ascending order. If order_by is not specified, it will order by default with create_time in descending order. Supported fields:
-
create_time
-
start_time
-
end_time
-
next_run_time
var
string
$this
static::build
parent
string
Required. The resource name of the Location to list the Schedules from.
Format: projects/{project}/locations/{location}
Please see Google\Cloud\AIPlatform\V1\ScheduleServiceClient::locationName()
for help formatting this field.