Summary
The Databricks CLI `--profile` fallback is fixed, and the SDK now requests fresh tokens from the CLI. Several breaking changes occurred in Vector Search endpoint scaling, and new API methods were added for workspace supervisor agents and various connector options.
Summary generated by brickster.ai. For the full changelog and any code/binary attachments, follow the GitHub link above.
More from databricks/databricks-sdk-java
New fields for pipeline refresh selection and checkpoint reset are available in `PipelineParams` and `PipelineTask` for Databricks Jobs. Additionally, new operational email custom recipient fields are added to `Setting` in the settings API.
This release adds comprehensive API methods for managing workspace assignments at both account and workspace levels. It also introduces support for Python operator tasks in Databricks Jobs and new fields for disaster recovery stable URLs, MLflow time windows, ingress network policies, and user API scopes.
Feature objects now include catalog, schema, creation, and name details, while listing features requires new catalog and schema parameters, which is a breaking change. GPU_XLARGE is a new workload type for serving models, and a field was removed from `RequestedResource`.
This release adds new services for disaster recovery, temporary volume credentials, and extensive methods for knowledge assistants. It also introduces new fields across various services and a breaking change removing the `connection` field from `SupervisorAgent` tools.
The SDK now automatically detects AI coding agents and appends agent information to HTTP request headers, while also removing the unused `experimentalIsUnifiedHost` field from `DatabricksConfig`. A bug fix addresses `X-Databricks-Org-Id` header issues for `SharesExtImpl.list()` on SPOG hosts, and several API method paths have changed, which are breaking changes.
This release adds Azure MSI authentication support and improves `.databrickscfg` default profile resolution. It also fixes issues with non-JSON error responses and Databricks CLI token scope mismatches, alongside introducing new API methods for various services like Catalog and Vector Search.