-
Notifications
You must be signed in to change notification settings - Fork 14k
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
OperationalError: (sqlite3.OperationalError) no such column: dbs.impersonate_user #4142
Comments
The first error is usually you upgrading superset but forgiving to run the migrations to update the db. The second looks like something that should have been fixed by #3111 |
The migration you are missing somehow is |
@mistercrunch looking at the migration output I pasted above, I do see the migration you're talking about (the 7th migration from the bottom). Are you saying I find the version that comes with that migration, downgrade to it, and re-run the migration? |
I uninstalled superset and re-installed 0.19.1 with pip.
When I run
And then I upgraded to the latest version and run the migrations again. I still get @xrmx @mistercrunch any thoughts on what I can try next? BTW, I use the default superset DB |
Isn't it strange that superset db upgrade created a new db? Are you sure your superset instance is not using a different database? |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
Could you please tell me how we can reset the db?
is really giving me hard time. I just want to reset it. |
Were you able to fix it somehow ? I am facing the same issue @bivav |
@BigDataArtist Now I am not working on superset but when I had error I just deleted that db and initialized the db from beginning. |
Please help!
Make sure these boxes are checked before submitting your issue - thank you!
I looked at a similar issue #3517 However, I don't understand how it was fixed.
Superset version
Expected results
A webpage displaying a list of Tables.
Actual results
Steps to reproduce
Just today, a co-worker reported a 500 internal server error running a query in SQL lab.
Attempting to fix the
AttributeError
issue by upgrading, I decided to upgrade but I have thisno such column: dbs.impersonate_user
issue now.I upgraded following the steps here: https://superset.incubator.apache.org/installation.html#upgrading
I did get some errors and warnings when running
db upgrade
.The text was updated successfully, but these errors were encountered: