ReleaseBytes
databricks Databricks Java SDK Releases · · 0.142.0

Databricks SDK Java v0.142.0: Streaming Body Fix and Billing/Catalog API Additions

sdkdatadatabricksengineermedia
patch

Databricks SDK Java version 0.142.0 fixes a bug where streaming uploads could send an empty body on retries, preventing data corruption and improving error handling for users of `files().upload()`. The release also introduces new fields and enum values to the billing and catalog APIs, enhancing configuration flexibility for these services. These changes primarily affect developers using the Java SDK for Databricks platform interactions, particularly those managing billing alerts or catalog policies.

  • →Add principalOverrides and scopeType fields for com.databricks.sdk.service.billing.AlertConfiguration
  • →Add resourceType field for com.databricks.sdk.service.billing.BudgetConfiguration
  • →Add resourceType field for com.databricks.sdk.service.billing.CreateBudgetConfigurationBudget
  • →Add principalOverrides and scopeType fields for com.databricks.sdk.service.billing.CreateBudgetConfigurationBudgetAlertConfigurations
  • →Add resourceType field for com.databricks.sdk.service.billing.UpdateBudgetConfigurationBudget
Enhancements (8) ›
  • Add principalOverrides and scopeType fields for com.databricks.sdk.service.billing.AlertConfiguration
  • Add resourceType field for com.databricks.sdk.service.billing.BudgetConfiguration
  • Add resourceType field for com.databricks.sdk.service.billing.CreateBudgetConfigurationBudget
  • Add principalOverrides and scopeType fields for com.databricks.sdk.service.billing.CreateBudgetConfigurationBudgetAlertConfigurations
  • Add resourceType field for com.databricks.sdk.service.billing.UpdateBudgetConfigurationBudget
  • Add grant field for com.databricks.sdk.service.catalog.PolicyInfo
  • Add BLOCK_USAGE enum value for com.databricks.sdk.service.billing.ActionConfigurationType
  • Add POLICY_TYPE_GRANT enum value for com.databricks.sdk.service.catalog.PolicyType
Fixes (1) ›

  • Fixed requests with a streaming body (e.g. files().upload()) silently uploading an empty body when retried. A single-use InputStream body is consumed by the first attempt, so retrying a retriable error (e.g. HTTP 503) re-sent an empty stream, which could write a 0-byte file or surface as a confusing error. The SDK no longer retries a streaming request once its body has been sent, and instead surfaces the original error so the caller can retry with a fresh stream

Read the original announcement →

https://github.com/databricks/databricks-sdk-java/releases/tag/v0.142.0

Related releases