-
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
Database error when upgrading from 1.4.1 to master #19100
Comments
I can replicate on Previously:
Seems linked to #16756, but actual migration that hasn't worked properly is FWIW, I'm using PostgreSQL as back-end db though. |
I got the same problem. My Log is similar:
|
Had the same issue when updating from 1.4.2 (deployed on Kubernetes using the Helm chart) to latest master. PostgreSQL as the database. |
Ok, I've found the issue. It appears migrations superset/superset/migrations/versions/f9847149153d_add_certifications_columns_to_slice.py Lines 29 to 30 in 9fc5e09
superset/superset/migrations/versions/f9847149153d_add_certifications_columns_to_slice.py Lines 29 to 30 in 156ac7d
What we need to do is move |
Fix PR: #19543 |
I though to report this so that it could be fixed in the next release.
When I upgrade an existing 1.4.1 instance that uses postgreSQL for metadata storage, I get an error and cannot use previously existing dashboards. (sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedColumn) column dbs.allow_file_upload does not exist)
The same error appears in the
supserset init
stage, so I will include the log below/How to reproduce the bug
image: apache/superset:1.4.1
toimage: apache/superset:master
Currently this is the DIGEST:sha256:23094797144b33a717c8d1d950825116bed97c1c4d6342d708b359279a31d83c
Expected results
Superset works as normal
Actual results
SQL error from the DB and superset dashboards do not work
Logs
Environment
master
FEATURE_FLAGS = {
'ENABLE_TEMPLATE_PROCESSING': True,
'DASHBOARD_RBAC': True,
'DASHBOARD_CROSS_FILTERS': True,
'VERSIONED_EXPORT': True,
'DASHBOARD_NATIVE_FILTERS': True,
'ROW_LEVEL_SECURITY': True,
}
Checklist
Make sure to follow these steps before submitting your issue - thank you!
No this is in master branch. The released version works fine.
The text was updated successfully, but these errors were encountered: