Superset to Dremio connectivity

1

Hi,

We have hosted Dremio and Superset on an AKS Cluster in Azure and we are trying to connect Superset to the Dremio Database(Lakehouse) for fetching some dashboards. We have installed all the required drivers(arrowflight, sqlalchemy_dremio and unixodc/dev) to establish the connection.

Strangely we are able not able to connect to Dremio from the Superset UI using the connection strings:

Here’s the error:

_(builtins.NoneType) None\n(Background on this error at: https://sqlalche.me/e/14/dbapi)", "error_type": "GENERIC_DB_ENGINE_ERROR", "level": "error", "extra": {"engine_name": "Dremio", "issue_codes": [{"code": 1002, "message": "Issue 1002 - The database returned an unexpected error."}]}}]_

However, while trying from inside the Superset pod, using this python script here, the connection goes through without any issues.

PS - One point to note is that, we have not enabled SSL certificates for our hostnames.

2

@lenoyjacob @balaji.ramaswamy - Hi Experts, Any suggestions here would be of much help.

3

@ramprasd89 Did you see the below already?

Also this Database error 1002 that is retuned seems very generic, can you check with Superset on how to get additional logging on this?

4

I have similar issue… I guess problem in sqlalchemy plugin… when I tried to connect trough
from pyarrow import flight - its working ok, but when I tried get data using sqlalchemy(I guess Superset use the same method) I got an error

E1031 18:32:27.780669000 8513643776 ssl_utils.cc:590] load_file: {“created”:“@1667226747.780654000”,“description”:“Failed to load file”,“file”:“/Users/voltrondata/github-actions-runner/_work/crossbow/crossbow/vcpkg/buildtrees/grpc/src/85a295989c-6cf7bf442d.clean/src/core/lib/iomgr/load_file.cc”,“file_line”:72,“filename”:“/usr/share/grpc/roots.pem”,“referenced_errors”:[{“created”:“@1667226747.780653000”,“description”:“No such file or directory”,“errno”:2,“file”:“/Users/voltrondata/github-actions-runner/_work/crossbow/crossbow/vcpkg/buildtrees/grpc/src/85a295989c-6cf7bf442d.clean/src/core/lib/iomgr/load_file.cc”,“file_line”:45,“os_error”:“No such file or directory”,“syscall”:“fopen”}]}
E1031 18:32:27.780682000 8513643776 ssl_security_connector.cc:420] Could not get default pem root certs.
E1031 18:32:27.780684000 8513643776 secure_channel_create.cc:88] Failed to create secure subchannel for secure name ‘localhost:32010’
E1031 18:32:27.780686000 8513643776 secure_channel_create.cc:48] Failed to create channel args during subchannel creation.
E1031 18:32:27.780691000 8513643776 ssl_security_connector.cc:420] Could not get default pem root certs.
E1031 18:32:27.780693000 8513643776 secure_channel_create.cc:88] Failed to create secure subchannel for secure name ‘localhost:32010’
E1031 18:32:27.780694000 8513643776 secure_channel_create.cc:48] Failed to create channel args during subchannel creation.

image
image1920×1084 198 KB