Catalog
DeprecatedAction required
Unity Catalog REST list operations will soon reject unpaginated requests with HTTP 400
From Databricks release notes (AWS)
Databricks will soon answer unpaginated calls to some Unity Catalog REST operations, such as list catalogs, schemas and tables, with HTTP 400. Until then they face stricter rate limits and HTTP 429 responses. Direct callers should set max_results=0 and follow next_page_token; current SDK and CLI releases already do. No date is given.
What to do
Update direct callers to set max_results=0 and page through results with next_page_token, or upgrade the SDK or CLI.
What to re-read
More from Catalog
- PreviewMetric views can record joins to other metric views with RELATIONSHIP constraints (Beta)
- ReleaseUnity Catalog permissions on system.ai now control which AI Functions users can run (GA)
- PreviewFiles API 3.0 for Unity Catalog volumes enters Beta with multipart uploads
- ReleaseService principal OAuth tokens can carry a custom identity claim for per-user row filtering