Cluster Access mode set to Shared on Databricks, results in connection refused on Exasol

[Gembo]

I am trying to run a TRUNCATE command on my exasol DWH from Databricks using the pyexasol. This works perfectly fine when I have the cluster access mode as "No Isolation Shared" which does not have access to our Unity Catalog. When I change the cluster access mode to "Shared" and now has access to Unity Catalog, the cluster fails to connect to Exasol DWH with the following error message:

"Could not connect to Exasol: [Errno 111] Connection refused"

Any ideas how to solve this?

[SSundaram]

Interesting. Did you try with "Single User" mode, which also has UC support? 

[Gembo]

@SSundaram "Single user" access mode works when connecting using pyexasol, but this cluster is being accessed by our whole Data Engineering team and would not really be a viable solution. 

[SSundaram]

Understood. So UC is not the problem, but the access mode is what causing this issue. There are few limitations with shared access mode on UC. I am guessing it might be the credentials passthrough, not sure. 

[Gembo]

It is not a problem of connectivity/firewall as I am able to connect using pyexasol when setting the access mode to different values on Databricks Cluster. Our Exasol and Databricks are not trial modes as these are our main DWH/Data Lakehouse for our data.