-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Unable to connect with Vertica #3232
Comments
Full stackstrace please. Also this driver looks a bit more maintained than the one you are using https://pypi.python.org/pypi/sqlalchemy-vertica |
@xrmx I tried the new package, got this error:
|
when using an incorrect credentials I get invalid username or password error. |
@hc000 none of the stacktraces you posted are superset issues and you need to use triple backquote to quote them otherwise they are unreadable. Better option is to open an issue to the vertica dialect with the first stackstrace and ask for help there. |
@xrmx I only used these python library because it was mentioned specifically in the superset documentation https://superset.incubator.apache.org/installation.html I followed the documentation for vertica and it doesn't work. I posted the errors above. It does seem like the issue is NOT with superset specifically, but the docs recommends those package and says it supports vertica. |
Notice: this issue has been closed because it has been inactive for 200 days. Feel free to comment and request for this issue to be reopened. |
Superset version
0.18.5
Hi everyone,
I'm trying to connect Superset with a Vertica database through Sources > Databases with the SQLAlchemy URI
vertica+vertica_python://user:passwd@hostname:5432/DB
and I got the following error:
ERROR: {"error": "Connection failed!\n\nThe error message returned was:\n'NoneType' object has no attribute '__getitem__'"}
I have already installed the Vertica connector (
pip install sqlalchemy-vertica-python
) and I have sucessfully connected to a Redshift database.Any ideas?
Sorry for my noobness...
Thanks in advance
The text was updated successfully, but these errors were encountered: