Open lloonngg opened 3 months ago
The error you're encountering, "TypeError: Table.init() takes from 2 to 4 positional arguments but 5 were given," during the superset db upgrade
process is indicative of a problem with how a Table
object is being initialized. This issue likely stems from a version mismatch or an incompatibility between the migration scripts and the version of SQLAlchemy being used by Superset.
To address this issue, you should:
Check SQLAlchemy Version: Ensure that the version of SQLAlchemy used by Superset is compatible with the migration scripts. Incompatibilities between versions could lead to unexpected errors during migrations.
Review Custom Code: If you have custom code or overrides in your Superset installation, review them to ensure they are not contributing to the issue. This includes any custom migration scripts or modifications to the Superset codebase.
Enable Detailed Logging: Turning on detailed logging for the migration process can help pinpoint exactly where the error occurs, providing more context on the erroneous call to Table.__init__()
.
Consult Documentation: Review the latest Apache Superset and SQLAlchemy documentation for any notes on migration issues or breaking changes in the versions you are upgrading to.
It's also worth noting that while SQLite is supported for Superset's metadata database, it's generally recommended for lightweight or development purposes only. For production environments, more robust databases like PostgreSQL or MySQL are recommended due to their better scalability and concurrency support.
To continue the conversation, mention @dosu.
Bug description
This issue is related to a prior one that was closed without a resolution Related issue
We are using Rancher Kubernetes 1.20.9. I don't think this is Kubernetes specific.
We were able to rebuild our Docker image including libraries to connect to various databases (pyodbc, dremio, sybase, etc.)
1.3.0 --> 1.5.0 (successful) 1.5.0 --> 1.5.3 (successful) 1.5.0 --> 2.0.0 (failed) 1.5.3 --> 2.0.0 (failed) 1.5.0 --> 3.1.3 (failed) 1.5.3 --> 3.1.3 (failed)
We are using sqlite for the database. When running
superset db upgrade
, we get this error below in the log. Any workarounds or solution for this?`INFO [alembic.runtime.migration] Context impl SQLiteImpl. INFO [alembic.runtime.migration] Will assume transactional DDL. INFO [alembic.runtime.migration] Running upgrade ad07e4fdbaba -> a9422eeaae74, new_dataset_models_take_2
How to reproduce the bug
superset db upgrade
Screenshots/recordings
No response
Superset version
3.1.3
Python version
3.10
Node version
I don't know
Browser
Not applicable
Additional context
No response
Checklist