Why does 'Add from Connection' take a long time to load the list of Entities from Databricks?

Created by Alexandru Sirbu, Modified on Fri, 13 Mar at 11:31 AM by Alexandru Sirbu

If Add from Connection takes a long time to load entities, the issue is not necessarily caused by WOODY.IO itself. In many cases, the delay is related to the configured Databricks cluster or to missing catalog and schema filters in the Databricks Connection.


The 'Add from Connection' function queries the catalog tables through the Databricks cluster configured in WOODY.IO. If that cluster is slow, the entity list will also load slowly. Performance may be affected even more if the same cluster is already being used by other users or workloads.


Another common reason is that the Connection is not restricted by catalog or schema. When no catalog or schema filter is set, WOODY.IO must retrieve all entities that the user can access. In environments with a large number of available objects, this can significantly increase loading time. In this case, the user appears to have access to more than 1,000 entities.


To improve performance, configure a specific catalog and schema in the Databricks Connection used by WOODY.IO. If you need to load all available tables across a large environment, using a more powerful Databricks cluster is recommended.


If you have any further questions, please feel free to Contact Us.

You can also refer to the WOODY.IO End User Documentation.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article