Skip to content
brickster.ai
All topics

Databricks SDK

Recent items mentioning Databricks SDK across the Databricks ecosystem — releases, news, videos, and community Q&A. Updated hourly.

28 recent items26 releases2 community threads
What's happening in Databricks SDKAI synthesis · updated 2h ago

The Databricks SDK for Go has been updated to v0.134.0, adding support for new fields in job pipeline refresh selections (full, flow, reset checkpoint) and operational email custom recipients 1. Community discussions on Reddit also touched upon the Databricks SDK 2 and a recovery script for Lakeflow SDP pipelines encountering DIFFERENT_DELTA_TABLE_READ_BY_STREAMING_SOURCE errors 3.

Generated daily from the 3 most recent items mentioning Databricks SDK. Click any [N] to jump to the source.

RedditDiscussion

Databricks-sdk

When using databricks-sdk in python. For the first time using the workspace client it gives a pop up for user login , but for the subsequent runs it gives authentication succeeded even after deleting the local cache tokens (.databricks/token-cache.json) Any insights , for how long the authentication stays or from where else we can delete the cache credentials , so the pop up can rework again?

21Economy_Ad68681w ago
RedditTutorial

If your Lakeflow SDP pipeline broke with DIFFERENT_DELTA_TABLE_READ_BY_STREAMING_SOURCE, here's a recovery script

I ran into this recently and wanted to share. A Delta table I was streaming from got dropped and recreated by an upstream team. Same name, same schema, but the new table has a fresh internal ID. Spark Structured Streaming checkpoints bind to that ID, so the next pipeline run error with: `[DIFFERENT_DELTA_TABLE_READ_BY_STREAMING_SOURCE] The streaming query was reading from an unexpected Delta table...` In open-source Spark you'd delete the checkpoint directory. Lakeflow SDP manages those paths internally, so that's not an option. The fix is the Pipelines API parameter `reset_checkpoint_selection` (added in `databricks-sdk` 0.100): pass a list of FQN flow names and start an update that clears only those checkpoints. Bronze/Silver/Gold targets stay untouched. I packaged the recovery as a sub-template in my Databricks bundle template repo. One CLI call ships the script (with a `--dry-run` flag), a workspace notebook variant, and a README: `databricks bundle init https://github.com/vmariiechko/databricks-bundle-template --template-dir assets/sdp-checkpoint-recovery` It also includes a fallback for environments where you can't pip-upgrade the SDK (for me it was the case when using the Databricks serverless runtime, which bundles its own SDK). Repo: https://github.com/vmariiechko/databricks-bundle-template/tree/main/assets/sdp-checkpoint-recovery Two gotchas worth knowing: - Flow names must be three-part Unity Catalog FQNs (`catalog.schema.table`), or you hit `IllegalArgumentException`. - Resetting checkpoints triggers a pipeline update; the API has no "reset only" mode. If you want the pipeline stopped after, cancel from the UI as soon as the call returns. Happy to answer questions or hear how you have handled this situation. P.S. Feel free to submit issues or PRs.

22Marik3481w ago