Superset upgrade from 0.35 to 0.36 failed
See original GitHub issueA clear and concise description of what the bug is.
Expected results
Upgraded to 0.36 version with existing dashboards, charts, databases, users etc.,
Actual results
Failed “superset db upgrade”
Screenshots
If applicable, add screenshots to help explain your problem.
How to reproduce the bug
- pip install apache-superset upgrade
- superset db upgrade
- I see there are new fields added to “tables”, “dbs”,“slices” which is causing issue.
- Unable to retain dashboards and charts.
Error:
INFO:superset.utils.logging_configurator:logging was configured successfully
/usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:202: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
"Flask-Caching: CACHE_TYPE is set to null, "
/usr/local/lib/python3.6/site-packages/pymysql/cursors.py:170: Warning: (3719, "'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.")
result = self._query(query)
DEBUG:asyncio:Using selector: EpollSelector
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1278, in _execute_context
cursor, statement, parameters, context
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 593, in do_execute
cursor.execute(statement, parameters)
File "/usr/local/lib/python3.6/site-packages/pymysql/cursors.py", line 170, in execute
result = self._query(query)
File "/usr/local/lib/python3.6/site-packages/pymysql/cursors.py", line 328, in _query
conn.query(q)
File "/usr/local/lib/python3.6/site-packages/pymysql/connections.py", line 517, in query
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
File "/usr/local/lib/python3.6/site-packages/pymysql/connections.py", line 732, in _read_query_result
result.read()
File "/usr/local/lib/python3.6/site-packages/pymysql/connections.py", line 1075, in read
first_packet = self.connection._read_packet()
File "/usr/local/lib/python3.6/site-packages/pymysql/connections.py", line 684, in _read_packet
packet.check_error()
File "/usr/local/lib/python3.6/site-packages/pymysql/protocol.py", line 220, in check_error
err.raise_mysql_exception(self._data)
File "/usr/local/lib/python3.6/site-packages/pymysql/err.py", line 109, in raise_mysql_exception
raise errorclass(errno, errval)
pymysql.err.InternalError: (1054, "Unknown column 'dbs.server_cert' in 'field list'")
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1278, in _execute_context
cursor, statement, parameters, context
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 593, in do_execute
cursor.execute(statement, parameters)
File "/usr/local/lib/python3.6/site-packages/pymysql/cursors.py", line 170, in execute
result = self._query(query)
File "/usr/local/lib/python3.6/site-packages/pymysql/cursors.py", line 328, in _query
conn.query(q)
File "/usr/local/lib/python3.6/site-packages/pymysql/connections.py", line 517, in query
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
File "/usr/local/lib/python3.6/site-packages/pymysql/connections.py", line 732, in _read_query_result
result.read()
File "/usr/local/lib/python3.6/site-packages/pymysql/connections.py", line 1075, in read
first_packet = self.connection._read_packet()
File "/usr/local/lib/python3.6/site-packages/pymysql/connections.py", line 684, in _read_packet
packet.check_error()
File "/usr/local/lib/python3.6/site-packages/pymysql/protocol.py", line 220, in check_error
err.raise_mysql_exception(self._data)
File "/usr/local/lib/python3.6/site-packages/pymysql/err.py", line 109, in raise_mysql_exception
raise errorclass(errno, errval)
pymysql.err.InternalError: (1051, "Unknown table 'superset.sqlite_sequence'")
Environment
(please complete the following information):
- superset version:
0.35
- python version:
3.6
- Mysql 8.0.17
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
- [x ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- I have reproduced the issue with at least the latest released version of superset.
- [x ] I have checked the issue tracker for the same issue and I haven’t found one similar.
Additional context
Manually updating each table is tedious task.
How to upgrade to latest version of superset without manually updating the Mysql tables?
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Superset upgrade from 0.35 to 0.36 failed #10364 - GitHub
A clear and concise description of what the bug is. Expected results Upgraded to 0.36 version with existing dashboards, charts, databases, ...
Read more >[GitHub] [incubator-superset] Fentonfi commented on issue #9736 ...
Hi, I am also facing similar issue while upgrading from superset 0.35.2 to 0.36.0. Here is the error, that I see when I...
Read more >Installation & Configuration - apache-superset - Read the Docs
With only the 2GB of RAM allocated by default, Superset will fail to start. Linux:
Read more >Upgrading Superset
Updating Superset Manually. To upgrade superset in a native installation, run the following commands: pip install apache-superset ...
Read more >airbnb/superset - Gitter
I was able to successfully add the datasource however when I try adding a chart, I see a connection refused error. Any pointers...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mistercrunch I uninstalled pymysql and install mysqlclient but issue still persists. @dbech no solution as of now, however planning some workarounds like manual db migrations.
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.