hotdata 0.17.0

Powerful data platform API for datasets, queries, and analytics.
Documentation
1
2
3
4
5
6
7
8
9
10
11
12
13
# JobResult

## Enum Variants

| Name | Description |
|---- | -----|
| BulkCreateDatabasesResult | What a finished background job produced. Absent while the job is `pending` or `running`, and absent for job types that report no payload.  Which shape you get is decided by the job's `job_type`, so read `job_type` first and then the matching object — the payload carries no discriminator of its own:  - `create_index` — the created index, in the same shape the index listing   returns. - `managed_load` — the load receipt: rows published and the table's schema   as published, in the same shape a synchronous load returns. - `bulk_create_databases` — the batch's counters: how many databases were   requested, how many were created, and whether the batch was stopped early.  The remaining job types — `noop` and the vacuum, compaction, and cleanup sweeps — report their outcome through `status` and `error_message` alone and leave this absent even once they finish. |
| IndexInfoResponse | What a finished background job produced. Absent while the job is `pending` or `running`, and absent for job types that report no payload.  Which shape you get is decided by the job's `job_type`, so read `job_type` first and then the matching object — the payload carries no discriminator of its own:  - `create_index` — the created index, in the same shape the index listing   returns. - `managed_load` — the load receipt: rows published and the table's schema   as published, in the same shape a synchronous load returns. - `bulk_create_databases` — the batch's counters: how many databases were   requested, how many were created, and whether the batch was stopped early.  The remaining job types — `noop` and the vacuum, compaction, and cleanup sweeps — report their outcome through `status` and `error_message` alone and leave this absent even once they finish. |
| LoadManagedTableResponse | What a finished background job produced. Absent while the job is `pending` or `running`, and absent for job types that report no payload.  Which shape you get is decided by the job's `job_type`, so read `job_type` first and then the matching object — the payload carries no discriminator of its own:  - `create_index` — the created index, in the same shape the index listing   returns. - `managed_load` — the load receipt: rows published and the table's schema   as published, in the same shape a synchronous load returns. - `bulk_create_databases` — the batch's counters: how many databases were   requested, how many were created, and whether the batch was stopped early.  The remaining job types — `noop` and the vacuum, compaction, and cleanup sweeps — report their outcome through `status` and `error_message` alone and leave this absent even once they finish. |

[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)