From c3ec33236d56e1081d2f14dfea9d568e5c79513f Mon Sep 17 00:00:00 2001 From: "databricks-ci-ghec-1[bot]" <184311507+databricks-ci-ghec-1[bot]@users.noreply.github.com> Date: Fri, 8 May 2026 11:24:14 +0000 Subject: [PATCH] Update SDK to 3c4239f03d7d476d7c9b3d60bc668451bd573863 --- .codegen/_openapi_sha | 2 +- NEXT_CHANGELOG.md | 2 +- .../src/main/java/com/databricks/sdk/WorkspaceClient.java | 7 ++----- .../sdk/service/catalog/TemporaryPathCredentialsAPI.java | 7 ++----- .../service/catalog/TemporaryPathCredentialsService.java | 7 ++----- 5 files changed, 8 insertions(+), 17 deletions(-) diff --git a/.codegen/_openapi_sha b/.codegen/_openapi_sha index 6e816b0eb..80f0f7fa2 100755 --- a/.codegen/_openapi_sha +++ b/.codegen/_openapi_sha @@ -1 +1 @@ -a499dda0f7802e37868d3f3076f62639165475d8 \ No newline at end of file +3c4239f03d7d476d7c9b3d60bc668451bd573863 \ No newline at end of file diff --git a/NEXT_CHANGELOG.md b/NEXT_CHANGELOG.md index f4a3ff685..a0e89431d 100755 --- a/NEXT_CHANGELOG.md +++ b/NEXT_CHANGELOG.md @@ -43,4 +43,4 @@ * Add `privateAccess` field for `com.databricks.sdk.service.settings.CustomerFacingIngressNetworkPolicy`. * Add `accountApi`, `accountDatabricksOne` and `accountUi` fields for `com.databricks.sdk.service.settings.CustomerFacingIngressNetworkPolicyRequestDestination`. * Add `scopeQualifier` field for `com.databricks.sdk.service.settings.CustomerFacingIngressNetworkPolicyWorkspaceApiDestination`. -* Add `displayName` and `previewPhase` fields for `com.databricks.sdk.service.settingsv2.SettingsMetadata`. \ No newline at end of file +* Add `displayName` and `previewPhase` fields for `com.databricks.sdk.service.settingsv2.SettingsMetadata`. diff --git a/databricks-sdk-java/src/main/java/com/databricks/sdk/WorkspaceClient.java b/databricks-sdk-java/src/main/java/com/databricks/sdk/WorkspaceClient.java index 8ae58fa89..3e8fe1fa1 100755 --- a/databricks-sdk-java/src/main/java/com/databricks/sdk/WorkspaceClient.java +++ b/databricks-sdk-java/src/main/java/com/databricks/sdk/WorkspaceClient.java @@ -1987,17 +1987,14 @@ public TagPoliciesAPI tagPolicies() { * reducing the risk of unauthorized access or misuse. To use the temporary path credentials API, * a metastore admin needs to enable the external_access_enabled flag (off by default) at the * metastore level. A user needs to be granted the EXTERNAL USE LOCATION permission by external - * location owner. For requests on existing external tables, user also needs to be granted the - * EXTERNAL USE SCHEMA permission at the schema level by catalog owner. + * location owner. For requests on existing external tables and external volumes, user also needs + * to be granted the EXTERNAL USE SCHEMA permission at the schema level by catalog owner. * *

Note that EXTERNAL USE SCHEMA is a schema level permission that can only be granted by * catalog owner explicitly and is not included in schema ownership or ALL PRIVILEGES on the * schema for security reasons. Similarly, EXTERNAL USE LOCATION is an external location level * permission that can only be granted by external location owner explicitly and is not included * in external location ownership or ALL PRIVILEGES on the external location for security reasons. - * - *

This API only supports temporary path credentials for external locations and external - * tables, and volumes will be supported in the future. */ public TemporaryPathCredentialsAPI temporaryPathCredentials() { return temporaryPathCredentialsAPI; diff --git a/databricks-sdk-java/src/main/java/com/databricks/sdk/service/catalog/TemporaryPathCredentialsAPI.java b/databricks-sdk-java/src/main/java/com/databricks/sdk/service/catalog/TemporaryPathCredentialsAPI.java index e56a66132..8ba3bec52 100755 --- a/databricks-sdk-java/src/main/java/com/databricks/sdk/service/catalog/TemporaryPathCredentialsAPI.java +++ b/databricks-sdk-java/src/main/java/com/databricks/sdk/service/catalog/TemporaryPathCredentialsAPI.java @@ -18,17 +18,14 @@ * the risk of unauthorized access or misuse. To use the temporary path credentials API, a metastore * admin needs to enable the external_access_enabled flag (off by default) at the metastore level. A * user needs to be granted the EXTERNAL USE LOCATION permission by external location owner. For - * requests on existing external tables, user also needs to be granted the EXTERNAL USE SCHEMA - * permission at the schema level by catalog owner. + * requests on existing external tables and external volumes, user also needs to be granted the + * EXTERNAL USE SCHEMA permission at the schema level by catalog owner. * *

Note that EXTERNAL USE SCHEMA is a schema level permission that can only be granted by catalog * owner explicitly and is not included in schema ownership or ALL PRIVILEGES on the schema for * security reasons. Similarly, EXTERNAL USE LOCATION is an external location level permission that * can only be granted by external location owner explicitly and is not included in external * location ownership or ALL PRIVILEGES on the external location for security reasons. - * - *

This API only supports temporary path credentials for external locations and external tables, - * and volumes will be supported in the future. */ @Generated public class TemporaryPathCredentialsAPI { diff --git a/databricks-sdk-java/src/main/java/com/databricks/sdk/service/catalog/TemporaryPathCredentialsService.java b/databricks-sdk-java/src/main/java/com/databricks/sdk/service/catalog/TemporaryPathCredentialsService.java index 4d1b81ece..a77a2663d 100755 --- a/databricks-sdk-java/src/main/java/com/databricks/sdk/service/catalog/TemporaryPathCredentialsService.java +++ b/databricks-sdk-java/src/main/java/com/databricks/sdk/service/catalog/TemporaryPathCredentialsService.java @@ -15,8 +15,8 @@ * the risk of unauthorized access or misuse. To use the temporary path credentials API, a metastore * admin needs to enable the external_access_enabled flag (off by default) at the metastore level. A * user needs to be granted the EXTERNAL USE LOCATION permission by external location owner. For - * requests on existing external tables, user also needs to be granted the EXTERNAL USE SCHEMA - * permission at the schema level by catalog owner. + * requests on existing external tables and external volumes, user also needs to be granted the + * EXTERNAL USE SCHEMA permission at the schema level by catalog owner. * *

Note that EXTERNAL USE SCHEMA is a schema level permission that can only be granted by catalog * owner explicitly and is not included in schema ownership or ALL PRIVILEGES on the schema for @@ -24,9 +24,6 @@ * can only be granted by external location owner explicitly and is not included in external * location ownership or ALL PRIVILEGES on the external location for security reasons. * - *

This API only supports temporary path credentials for external locations and external tables, - * and volumes will be supported in the future. - * *

This is the high-level interface, that contains generated methods. * *

Evolving: this interface is under development. Method signatures may change.