| Method and Description |
|---|
| com.databricks.sdk.core.DatabricksConfig.getAzureUseMSI()
Use
DatabricksConfig.getAzureUseMsi() instead. |
| com.databricks.sdk.core.DatabricksConfig.getOidcEndpoints()
Use
DatabricksConfig.getDatabricksOidcEndpoints() instead. This method incorrectly returns
Azure OIDC endpoints when azure_client_id is set, even for Databricks OAuth flows that
don't use Azure authentication. This caused bugs where Databricks M2M OAuth would fail when
ARM_CLIENT_ID was set for other purposes. Use instead: - getDatabricksOidcEndpoints(): For
Databricks OAuth (oauth-m2m, external-browser, etc.). -
getAzureEntraIdWorkspaceEndpoints(): For Azure Entra ID OIDC endpoints. |
| com.databricks.sdk.core.DatabricksConfig.setAzureUseMSI(boolean)
Use
DatabricksConfig.getAzureUseMsi() instead. |
| Constructor and Description |
|---|
| com.databricks.sdk.support.Paginator(RQ, Function<RQ, RS>, Function<RS, Collection<T>>, Function<RS, RQ>)
Use
Paginator.newTokenPagination(RQ, java.util.function.Function<RQ, RS>, java.util.function.Function<RS, java.util.Collection<T>>, java.util.function.Function<RS, RQ>) or Paginator.newOffsetPagination(RQ, java.util.function.Function<RQ, RS>, java.util.function.Function<RS, java.util.Collection<T>>, java.util.function.Function<RS, RQ>) instead, which make
the pagination strategy explicit. Token-based APIs must use Paginator.newTokenPagination(RQ, java.util.function.Function<RQ, RS>, java.util.function.Function<RS, java.util.Collection<T>>, java.util.function.Function<RS, RQ>) to
avoid stopping early on an empty page that still carries a next-page token. |
Copyright © 2026. All rights reserved.