-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Database migration issue with catalog migration (catalog perm) #30596
Comments
Hey @otrebor! I'm here to help you with any bugs, questions, or contributions. Let's tackle this issue together! The error you're encountering seems to be related to the Here are a few steps you can take to troubleshoot and potentially resolve the issue:
If these steps don't resolve the issue, consider isolating the problem by creating a minimal setup to reproduce the error, which might help in identifying the root cause. |
Bug description
We are trying to upgrade our superset instance to 410rc2-py310
when we start superset, we get this error while the migration scripts are trying to update the catalog:
I can't really understand if it's a configuration problem or a bug. The connection string seems fine and previous tables are updated.
we see other issues like
#29492
#29728
but i don't think that's the problem for us.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.10
Node version
16
Browser
Chrome
Additional context
Checklist
The text was updated successfully, but these errors were encountered: