Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error connecting Apache Superset to CrateDB Cloud #95

Closed
amotl opened this issue Mar 6, 2024 · 4 comments
Closed

Error connecting Apache Superset to CrateDB Cloud #95

amotl opened this issue Mar 6, 2024 · 4 comments

Comments

@amotl
Copy link
Member

amotl commented Mar 6, 2024

Problem

@wierdvanderhaar reported an error without much further information when connecting Apache Superset to CrateDB Cloud, while roughly following the setup instructions 1, omitting workstation setup details.

The connection URL is:

crate://tsadmin:[email protected]:5432/doc?sslmode=require

image

Footnotes

  1. https://community.cratedb.com/t/set-up-apache-superset-with-cratedb/1716

@amotl
Copy link
Member Author

amotl commented Mar 6, 2024

Using the ?ssl=true suffix on the connection URL did not change anything. Wierd reported it's the same error.

@amotl
Copy link
Member Author

amotl commented Mar 6, 2024

Thoughts

What about omitting doc within the URL path, because CrateDB does not know about databases?

The correct way to address a schema in SQLAlchemy would be by using the schema query parameter, like ?schema=doc, but I'd always recommend to omit it completely when troubleshooting, to verify if basic connectivity works.

Related

@amotl
Copy link
Member Author

amotl commented Mar 6, 2024

Now I am seeing it. You can't use the CrateDB SQLAlchemy dialect to connect to the PostgreSQL port, because the dialect currently speaks HTTP only. That other patch may improve the situation in this regard.

@amotl
Copy link
Member Author

amotl commented Mar 6, 2024

@wierdvanderhaar says:

Default port works, sorry for the confusion!

Thanks. Sorry for noticing late!

@amotl amotl closed this as completed Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant