Amorphic Schedule provides a self-service data ingestion mechanism which provides a mechanism for batch and streaming data ingestion on a scheduled basis.
A Schedule can be created using the ‘+’ icon on the top right of page under ‘SCHEDULES’ section.
In order to create a schedule, User needs to specify all the mandatory requirements.
Schedule Name: A Unique name of Schedule that User wants to Create
Description: Brief description of the Schedule
Type of Job: User needs to choose the type of Job from the dropdown list. Below are the list of options available for schedule.
ETL Job: This option is used to schedule an ETL job
JDBC CDC: This option is used to Sync data between DWH to S3 for CDC related tasks, Please note that only tasks which have SyncToS3 option setting as yes will be shown and can be scheduled.
Data Ingestion: Data ingestion job for normal JDBC connections.
JDBC Full Load: This option is used to schedule a JDBC BulkDataLoad full-load task.
Notification Settings: User can choose the type of notifications he may want to receive
All: User will receive notification via emails for all events
Error-Only: User will receive notification via emails only when application encounters an error
Schedule Time: The user can choose the schedule time whether to be On-Time or On-Demand.
On-Demand schedules can be run as per the need.
User can disable a schedule to stop running the time-based schedule as per requirement. Time based schedules require a schedule expression.
Once a schedule is created for a specific job, the schedule can be using the “Run Schedule’ Option available at the top right icon on the page. There are multiple options available to perform on the scheduled job - Run Schedule, Disable Schedule, Clone Schedule and Delete Schedule.
The execution status indicates the current status of the scheduled job whether is it running, successful or failed.
Once the schedule execution is completed, Email notification will be sent based on the notification setting and schedule execution status. Below are the different scenarios: