Jobs Download
Description
Clones a remote job to your local machine, under a new directory with the name of thejob_id.
Sample
Parameters
| Option | Description |
|---|---|
job_root | The s3_root (known as the job root) of the job to clone. Can be found in Job Details or in the URL of the hotglue job page. |
The job root is of the form: tenant_id/flows/flow_id/jobs/2025/01/1/01/01/job_id
Jobs List
Description
Lists jobs across the hotglue environment. You can filter the results by tenant, connector, status, and date range.Sample
Parameters
| Option | Default | Description |
|---|---|---|
--count | 10 | Number of jobs to return, from 1-100. |
--page | 1 | Page of results to return. |
--status | Job status to filter on. Supports multiple comma-separated statuses. | |
--tenant | ||
-u | Tenant ID to filter on. | |
--taps | One or more taps to filter on. Multiple taps must be comma-separated. | |
--targets | One or more targets to filter on. Multiple targets must be comma-separated. | |
--from | Start date for the query, formatted as YYYY-MM-DD. | |
--to | End date for the query, formatted as YYYY-MM-DD. | |
--env | ||
-e | Environment ID to query jobs for. |
Jobs Status
Description
Polls the status of a job using its job root.Sample
Parameters
| Option | Default | Description |
|---|---|---|
--job-root | Required. S3 root of the job to poll. | |
--flow | ||
-f | Flow ID for the job. | |
--tenant | ||
-u | default | Tenant ID for the job. |
--env | ||
-e | Environment ID for the job. |
Jobs Run
Description
Runs a V1 or V2 job for a tenant.Sample
--v2 with --connector-id and --job-type:
Parameters
Options that accept objects should be passed as JSON strings.| Option | Default | Description |
|---|---|---|
--flow | ||
-f | Flow ID to run the job for. | |
--tenant | ||
-u | default | Tenant ID to run the job for. |
--env | ||
-e | Environment ID to run the job for. | |
--v2 | false | Run a V2 job. Requires --connector-id and --job-type. |
--tap | Source of the V1 job. | |
--connector-id | Connector ID to run for V2 jobs. | |
--job-type | V2 job type. Must be read or write. | |
--job-name | Name for the job. | |
--state | JSON object with extra context to use in the job. | |
--override-start-date | Date to start syncing data from. | |
--override-end-date | Date to sync data until. | |
--reset-source-state | false | Run the job as a full sync. |
--streaming-job | false | Run in streaming mode. |
--override-selected-tables | JSON object with a temporary unified schema object selection. | |
--override-field-map | JSON object with a temporary field map. | |
--override-source-config | JSON object with a temporary source config override. | |
--override-target-config | JSON object with a temporary target config override. | |
--override-connector-config | JSON object with a temporary connector config override. | |
--environment-variables | JSON object with job environment variable overrides. |
Jobs Bulk Run
Description
Runs multiple jobs in bulk from a JSON file. The command reads a JSON file containing an array of job configurations, validates each job, checks flow versions, and runs all jobs in parallel. Results are displayed in a table format with a summary of successes and failures.Sample
jobs.json):
Parameters
| Option | Description |
|---|---|
--file -f | Required. Path to JSON file containing an array of job objects to run. Each job object must include flow and tenant fields. Additional job arguments can be included and will be passed to the body of the job trigger endpoint. |
Jobs Bulk Kill
Description
Kills multiple running jobs in bulk. The command fetches jobs from the last month with statusesJOB_CREATED, SYNC_STARTED, SYNC_SUCCESS, ETL_STARTED, ETL_SUCCESS, or EXPORT_STARTED, optionally filters them by tenant IDs and/or flow IDs, and kills all matching jobs in parallel. Results are displayed in a table format with a summary of successes and failures.
Sample
Parameters
| Option | Description |
|---|---|
--tenant-ids --tenants | Comma-separated list of tenant IDs to filter jobs by. Only jobs belonging to these tenants will be killed. If not provided, all matching jobs will be considered. |
--flow-ids | |
--flows | Comma-separated list of flow IDs to filter jobs by. Only jobs for these flows will be killed. If not provided, all matching jobs will be considered. |
--reason | Optional reason for killing the jobs. This reason will be included in the kill request for all jobs. |
Jobs Bulk Retrigger
Description
Retriggers multiple jobs in bulk from a JSON file containing job roots. The command reads a JSON file containing an array of job root strings, groups them by tenant and flow, and retriggers jobs with parallel processing across groups and sequential processing within each group. For each group, the command waits for a job to complete before retriggering the next job in that group. Results are displayed in a table format with a summary of successes and failures.Sample
jobRoots.json):
Parameters
| Option | Description |
|---|---|
--file -f | Required. Path to JSON file containing an array of job root strings to retrigger. Each job root must follow the format: {tenantId}/flows/{flowId}/jobs/.... Jobs are automatically grouped by tenant and flow, and processed sequentially within each group (waiting for completion) while groups are processed in parallel. |