superset upgrade failed from v0.27 to v0.35
See original GitHub issueHi :
I upgraded my software according to the manual, from v0.27 to v0.35. After upgrading, I found that the Sources was not available, but the Security and manage were OK. The error message as follows:
ERROR: {"error": "Connection failed!\n\nThe error message returned was:\n(sqlite3.OperationalError) no such column: dbs.allow_run_sync [SQL: 'SELECT dbs.created_on AS dbs_created_on, dbs.changed_on AS dbs_changed_on, dbs.id AS dbs_id, dbs.verbose_name AS dbs_verbose_name, dbs.database_name AS dbs_database_name, dbs.sqlalchemy_uri AS dbs_sqlalchemy_uri, dbs.password AS dbs_password, dbs.cache_timeout AS dbs_cache_timeout, dbs.select_as_create_table_as AS dbs_select_as_create_table_as, dbs.expose_in_sqllab AS dbs_expose_in_sqllab, dbs.allow_run_sync AS dbs_allow_run_sync, dbs.allow_run_async AS dbs_allow_run_async, dbs.allow_ctas AS dbs_allow_ctas, dbs.allow_dml AS dbs_allow_dml, dbs.force_ctas_schema AS dbs_force_ctas_schema, dbs.allow_multi_schema_metadata_fetch AS dbs_allow_multi_schema_metadata_fetch, dbs.extra AS dbs_extra, dbs.perm AS dbs_perm, dbs.impersonate_user AS dbs_impersonate_user, dbs.created_by_fk AS dbs_created_by_fk, dbs.changed_by_fk AS dbs_changed_by_fk \\nFROM dbs \\nWHERE dbs.database_name = ?\\n LIMIT ? OFFSET ?'] [parameters: ('kylin', 1, 0)] (Background on this error at: http://sqlalche.me/e/e3q8)"}
some body please help me,thanks!
Screenshots
Environment
- superset version:
0.35.2
- python version:
3.6.4
- flask version:
1.1.1
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top GitHub Comments
@jsynl What database are you using? Superset will use SQLite as the database by default. If there is no special config, it will be saved in
If you need to reinstall and there is no important data, you can try removing superset.db
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
.pinned
to prevent stale bot from closing the issue.