Resolving Inbound Delta Share Errors Caused by Unsupported View Dependencies

Overview

If you see an error when trying to connect or update your inbound Delta Share, it may be caused by a view dependency that Delta Sharing does not support. This often happens when a shared view depends on another view, rather than directly on a Delta table.

 

Why This Happens

Delta Sharing supports only the following types of objects:

  • Managed Delta tables

  • External Delta tables

  • Simple views (that do not depend on other views)

If a shared view references another Delta shared view, the connection will fail because nested or dependent views are not supported by the Delta Sharing protocol.

Common Symptoms

You might notice one or more of these signs:

  • An error appears when selecting or editing a bridge table.

  • You are unable to unselect or reconfigure the affected view.

  • The inbound Delta Share previously worked but started failing recently due to a change in view dependencies.

How to Fix the Issue

  1. Identify the affected view.
    Check which view is causing the error — it often appears in the error message (for example: customer_1p_view).

  2. Check for dependencies.
    Open the view definition in Databricks and verify whether it references another view that’s also part of the Delta Share.

  3. Refactor the view.

    • Remove or replace the dependency on another view.

    • Convert the referenced view into a Delta table, and update your main view to reference that table instead.

  4. Re-share or refresh the view.
    Once dependencies are corrected, re-add the view to your Delta Share or refresh your inbound configuration in Amperity.

Example Scenario

A user encountered an inbound Delta Share error after modifying a Databricks view. The issue occurred because the shared view depended on another shared view. After converting the dependent view into a Delta table and updating the main view, the inbound share started working again.

Summary

  • Delta Sharing does not support nested or dependent views.

  • Ensure shared views only reference Delta tables.

  • Refactor or replace dependent views to restore the connection.

  • Once dependencies are fixed, your inbound Delta Share will sync normally.

Applies To

  • Inbound Delta Share configurations

  • Databricks environments using Delta Sharing

  • Bridge table or view selection errors during configuration