Package com.google.cloud.aiplatform.v1

Interface ScheduleServiceGrpc.AsyncService

    • Method Detail

      • createSchedule

        default void createSchedule​(CreateScheduleRequest request,
                            io.grpc.stub.StreamObserver<Schedule> responseObserver)
         Creates a Schedule.

      • deleteSchedule

        default void deleteSchedule​(DeleteScheduleRequest request,
                            io.grpc.stub.StreamObserver<com.google.longrunning.Operation> responseObserver)
         Deletes a Schedule.

      • getSchedule

        default void getSchedule​(GetScheduleRequest request,
                         io.grpc.stub.StreamObserver<Schedule> responseObserver)
         Gets a Schedule.

      • pauseSchedule

        default void pauseSchedule​(PauseScheduleRequest request,
                           io.grpc.stub.StreamObserver<com.google.protobuf.Empty> responseObserver)
         Pauses a Schedule. Will mark
 [Schedule.state][google.cloud.aiplatform.v1.Schedule.state] to 'PAUSED'. If
 the schedule is paused, no new runs will be created. Already created runs
 will NOT be paused or canceled.

      • resumeSchedule

        default void resumeSchedule​(ResumeScheduleRequest request,
                            io.grpc.stub.StreamObserver<com.google.protobuf.Empty> responseObserver)
         Resumes a paused Schedule to start scheduling new runs. Will mark
 [Schedule.state][google.cloud.aiplatform.v1.Schedule.state] to 'ACTIVE'.
 Only paused Schedule can be resumed.
 When the Schedule is resumed, new runs will be scheduled starting from the
 next execution time after the current time based on the time_specification
 in the Schedule. If [Schedule.catchUp][] is set up true, all
 missed runs will be scheduled for backfill first.

      • updateSchedule

        default void updateSchedule​(UpdateScheduleRequest request,
                            io.grpc.stub.StreamObserver<Schedule> responseObserver)
         Updates an active or paused Schedule.
 When the Schedule is updated, new runs will be scheduled starting from the
 updated next execution time after the update time based on the
 time_specification in the updated Schedule. All unstarted runs before the
 update time will be skipped while already created runs will NOT be paused
 or canceled.