Patrick-Boerzel-Qunis opened a new issue, #24389: URL: https://github.com/apache/superset/issues/24389
We have an dremio and superset installation on kubernetes. When we create a database connection to dremio I get an successful test connection "Connection looks good". As "Supported Databases" we use "Other" and as connection string we have something like that: "dremio+flight://<username>:<pat>@<host>:32010/<dbname>?UseEncryption=false&DisableCertificateVerification=true" where all variables are urlencoded because those can contain special characters like '='. But when we create that database connection, it shows the error:  But the connection is created anyway. When I test that connection, it can't fetch the schema, and shows errors. Neither in SQLLab, nor in create datasets. But when choosing that new connection in SQLLab without choosing a schema, the query runs successfully and can be saved as new Dataset. That can then also used on charts and everything. Last test was with following versions, but we also tried with some older ones. superset-image: apache/superset:ebca20b80050b90a5c361358e0d582d140ccfc85 sqlalchemy_dremio version: 3.0.3 dremio version: 24.1.0 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
