Skip to main content

Troubleshoot common sharing issues in Delta Sharing

The following sections describe common errors that might occur when you try to access data in a share.

Resource limit exceeded errors​

Issue: Your query on a shared table returns the error RESOURCE_LIMIT_EXCEEDED.

You may see either of these errors:

  • "RESOURCE_LIMIT_EXCEEDED","message":"The table metadata size exceeded limits"
  • "RESOURCE_LIMIT_EXCEEDED","message":"The number of files in the table to return exceeded limits, consider contact your provider to optimize the table"

Possible causes: There are limits on the number of files in metadata allowed for a shared table.

Recommended fix: To learn how to resolve either of these issues, see RESOURCE_LIMIT_EXCEEDED error when querying a Delta Sharing table in the Databricks Knowledge Base.

Vacuumed data file issue​

Issue: You see an error message that throws a “404 The specified [path|key] does not exist” exception.

Spark error examples:

java.lang.Throwable: HTTP request failed with status: HTTP/1.1 404 The specified path does not exist.

or

HTTP request failed with status: HTTP/1.1 404 Not Found <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message>

Possible cause: Typically you see this error because the data file corresponding to the pre-signed URL is vacuumed in the shared table and the data file belongs to a historical table version.

Workaround: Query the latest snapshot.

Shared materialization asset issue​

Issue: Your query on a shared view, materializaed view, or streaming table returns the error DS_MATERIALIZATION_QUERY_FAILED.

You may see this error:

  • "DS_MATERIALIZATION_QUERY_FAILED": "The shared asset could not be materialized due to the asset not being accessible in the materialization workspace. Please ask data provider to contact :re[DB] support to override the materialization workspace."

Possible causes: The provider does not have read-write access to the asset they are trying to share.

Recommended fix: Contact your data provider to ensure they have read-write access to the shared data asset.

Last updated on