Summary
This release introduces new methods for Lakeview and Postgres services, including `revert()` for Lakeview and `undeleteBranch()` for Postgres, along with new fields across various services like Jobs and IAM. Several breaking changes require `actionType` and `resourceId` for bundle operations, `cliVersion` for bundle versions, and alter the `tags` field for Marketplace listings and pagination for cluster events.
Summary from the captured archive. Follow the original source for full context.
More from databricks/databricks-sdk-java
Databricks SDK for Java v0.172.0 fixes CLI authentication so that small wrapper scripts, such as launcher scripts or version manager shims, are no longer mistaken for the legacy Python CLI, which now only applies to the pip entry point. The release also adds budget spend status methods to the account budgets service and an aiFunctionTask field across the jobs task types, with matching aiFunctionTaskOutput on run output.
Databricks SDK for Java v0.171.0 adds AgentKit permission methods for memory and session stores, Feature Engineering materialization set methods, and new fields across data quality, jobs, ML, pipelines, and sandbox APIs. The release also adds refresh-by-path selection fields to pipeline updates and a fileOutput option on jobs SQL outputs.
Release v0.170.0 adds startEndpoint() and stopEndpoint() methods for vector search endpoints, along with new STARTING, STOPPING, and STOPPED status values. It also adds OneDrive ingestion support for pipelines, an includeExternalSpend option for budgets, and new relativeError, TableTrigger, and regex fields.
Release v0.169.0 adds sdpSource to the ML DataSource, and adds customerVersionLabel, maxDbu, and reydenClusterSizeMultiplier to SQL warehouse create, edit, and get responses. It also removes the replicationConfig field from CreateShare and ShareInfo, which is a breaking change for Sharing API users.
The SDK adds file and directory management methods to the sandbox service alongside a new duration target field across Jobs API run and configuration models. Additionally, it introduces secret fields for Catalog connections, governed tags for policies, and replication tracking fields for disaster recovery failover groups.