Databricks ingestion run history (audit)
Paginated Databricks ingestion runs for the tenant, newest activity first.
Scoped to loader runs (databricks_loader_*) — the family this audit categorizes. Tenant-wide, with no per-connection scoping: loader runs leave global_tasks.data_store_id null, so nothing attributes a loader run to the connection that produced it and a data_store_id filter would match zero rows. (Only databricks_extractor_* runs carry data_store_id, and then only recently; Last Sync in crud.sync uses those for attribution, but they are a different run family and outside this loader-activity feed.)
status is enum-typed so an unknown value is a 422 from FastAPI. Left as free text it reaches Postgres as a cast to global_task_status_type and comes back as an unexplained 500.
Query parameters
Filter to these global_tasks statuses (e.g. completed, ingestion_failed).
Filter to these global_tasks statuses (e.g. completed, ingestion_failed).
Which ingestion family a run belongs to, for grouping the audit table.
Filter to one ingestion family (system_tables, cloud_cost, ...).
Page number
Page number
Page size
Page size
Headers
Response
Successful Response
Changes
Changed in 1 of the 29 revisions of this API.1
- ○
endpoint added
endpoint-added
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○