The data catalog's OCID.
OCID of the user who created this job.
Unique key of the data asset to which this job applies, if the job involves a data asset.
Detailed description of the job.
A user-friendly display name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
Error code returned from the latest job execution for this job. Useful when the latest Job execution is in FAILED state.
Error message returned from the latest job execution for this job. Useful when the latest Job Execution is in a FAILED state.
The total number of executions for this job schedule. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Array of the executions summary associated with this job.
Unique key of the glossary to which this job applies.
The unique key of the job definition resource that defined the scope of this job.
The display name of the job definition resource that defined the scope of this job.
Type of the job.
Unique key of the job.
Lifecycle state of the job, such as running, paused, or completed.
Interval on which the job will be run. Value is specified as a cron-supported time specification "nickname". The following subset of those is supported: @monthly, @weekly, @daily, @hourly. For metastore sync, an additional option @default is supported, which will schedule jobs at a more granular frequency.
Type of job schedule that is inferred from the scheduling properties.
The date and time the job was created, in the format defined by RFC3339. Example: {@code 2019-03-25T21:10:29.600Z}
The date and time of the most recent execution for this job, in the format defined by RFC3339. Example: {@code 2019-03-25T21:10:29.600Z}
Date that the schedule should be operational. An RFC3339 formatted datetime string.
Time that this job was last updated. An RFC3339 formatted datetime string.
OCID of the user who updated this job.
URI to the job instance in the API.
Details of a job. Jobs are scheduled instances of a job definition.