Non-existent schema on redeployment of DAB with external volumes.

toast_2001
New Contributor II

‎03-23-2026 01:45 AM

Hi all,

DAB issue.

My setup:

  • Running CLI v0.294 on Python 3.12.11.
  • Deployement is mode direct and using standard serverless compute.
  • External locations in ADLS ST Container (container per ext loc).

I'm attempting to deploy a bundle according to the following config.

config_file.png

First bundle deployment is successful with no validation errors. On redeployment of the bundle (even with no changes), the deployment fails with the following error (as described by the second image):

Error: cannot skip resources.schemas.landing: failed to read remote state: failed to refresh remote state id=demo.landing: Schema 'demo.landing' does not exist. (404 SCHEMA_DOES_NOT_EXIST)

Results from my debugging:

  • Removal of the resources.volumes block fixes the issue and I can redeploy everytime.
  • On redeployment, the UC seems to "destroy" the schemas rather then skip over unchanged - even though the error suggests a skip was attempted.
  • Hardcoding the values for schema name in the volumes block returns the same error.
  • Removal of the experimental skip_name_prefix_for_schema config did not resolve the issue.

example_error.png

The external volumes represent an ingestion location for databricks to attach to, its kind of crucial they deploy with the DAB for every update, especially if this thing is sitting in production.

Open to any work arounds too.

Thanks for your time.

Labels:
0 Kudos