You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "Nimishbansal-16 (via GitHub)" <gi...@apache.org> on 2025/05/19 08:44:05 UTC
[D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
GitHub user Nimishbansal-16 created a discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
Hi, i upgraded my superset from 4.0.0 to 4.1.2. After upgrade i was able to bring superset up but on ui i am getting error -
`An error occurred while fetching charts: (MySQLdb.OperationalError) (1054, "Unknown column 'slices.catalog_perm' in 'field list'")
[SQL: SELECT count(*) AS count_1
FROM (SELECT slices.uuid AS slices_uuid, slices.created_on AS slices_created_on, slices.changed_on AS slices_changed_on, slices.id AS slices_id, slices.slice_name AS slices_slice_name, slices.datasource_id AS slices_datasource_id, slices.datasource_type AS slices_datasource_type, slices.datasource_name AS slices_datasource_name, slices.viz_type AS slices_viz_type, slices.params AS slices_params, slices.query_context AS slices_query_context, slices.description AS slices_description, slices.cache_timeout AS slices_cache_timeout, slices.perm AS slices_perm, slices.schema_perm AS slices_schema_perm, slices.catalog_perm AS slices_catalog_perm, slices.last_saved_at AS slices_last_saved_at, slices.last_saved_by_fk AS slices_last_saved_by_fk, slices.certified_by AS slices_certified_by, slices.certification_details AS slices_certification_details, slices.is_managed_externally AS slices_is_managed_externally, slices.external_url AS slices_external_url, slices.created_by_fk AS slices_created_by
_fk, slices.changed_by_fk AS slices_changed_by_fk, changed_by.id AS changed_by_id, changed_by.first_name AS changed_by_first_name, changed_by.last_name AS changed_by_last_name, changed_by.username AS changed_by_username, changed_by.password AS changed_by_password, changed_by.active AS changed_by_active, changed_by.email AS changed_by_email, changed_by.last_login AS changed_by_last_login, changed_by.login_count AS changed_by_login_count, changed_by.fail_login_count AS changed_by_fail_login_count, changed_by.created_on AS changed_by_created_on, changed_by.changed_on AS changed_by_changed_on, changed_by.created_by_fk AS changed_by_created_by_fk, changed_by.changed_by_fk AS changed_by_changed_by_fk, created_by.id AS created_by_id, created_by.first_name AS created_by_first_name, created_by.last_name AS created_by_last_name, created_by.username AS created_by_username, created_by.password AS created_by_password, created_by.active AS created_by_active, created_by.email AS created_by_email,
created_by.last_login AS created_by_last_login, created_by.login_count AS created_by_login_count, created_by.fail_login_count AS created_by_fail_login_count, created_by.created_on AS created_by_created_on, created_by.changed_on AS created_by_changed_on, created_by.created_by_fk AS created_by_created_by_fk, created_by.changed_by_fk AS created_by_changed_by_fk, last_saved_by.id AS last_saved_by_id, last_saved_by.first_name AS last_saved_by_first_name, last_saved_by.last_name AS last_saved_by_last_name, last_saved_by.username AS last_saved_by_username, last_saved_by.password AS last_saved_by_password, last_saved_by.active AS last_saved_by_active, last_saved_by.email AS last_saved_by_email, last_saved_by.last_login AS last_saved_by_last_login, last_saved_by.login_count AS last_saved_by_login_count, last_saved_by.fail_login_count AS last_saved_by_fail_login_count, last_saved_by.created_on AS last_saved_by_created_on, last_saved_by.changed_on AS last_saved_by_changed_on, last_saved_by.cre
ated_by_fk AS last_saved_by_created_by_fk, last_saved_by.changed_by_fk AS last_saved_by_changed_by_fk, tables.uuid AS tables_uuid, tables.created_on AS tables_created_on, tables.changed_on AS tables_changed_on, tables.id AS tables_id, tables.description AS tables_description, tables.default_endpoint AS tables_default_endpoint, tables.is_featured AS tables_is_featured, tables.filter_select_enabled AS tables_filter_select_enabled, tables.offset AS tables_offset, tables.cache_timeout AS tables_cache_timeout, tables.params AS tables_params, tables.perm AS tables_perm, tables.schema_perm AS tables_schema_perm, tables.catalog_perm AS tables_catalog_perm, tables.is_managed_externally AS tables_is_managed_externally, tables.external_url AS tables_external_url, tables.table_name AS tables_table_name, tables.main_dttm_col AS tables_main_dttm_col, tables.database_id AS tables_database_id, tables.fetch_values_predicate AS tables_fetch_values_predicate, tables.schema AS tables_schema, tables.cat
alog AS tables_catalog, tables.sql AS tables_sql, tables.is_sqllab_view AS tables_is_sqllab_view, tables.template_params AS tables_template_params, tables.extra AS tables_extra, tables.normalize_columns AS tables_normalize_columns, tables.always_filter_main_dttm AS tables_always_filter_main_dttm, tables.created_by_fk AS tables_created_by_fk, tables.changed_by_fk AS tables_changed_by_fk
FROM slices LEFT OUTER JOIN ab_user AS changed_by ON slices.changed_by_fk = changed_by.id LEFT OUTER JOIN ab_user AS created_by ON slices.created_by_fk = created_by.id LEFT OUTER JOIN ab_user AS last_saved_by ON slices.last_saved_by_fk = last_saved_by.id LEFT OUTER JOIN tables ON slices.datasource_id = tables.id AND slices.datasource_type = %s) AS anon_1]
[parameters: ('table',)]
(Background on this error at: https://sqlalche.me/e/14/e3q8)`
Steps followed for upgrade -
pip install apache-superset==4.1.2
superset db upgrade
This gave an error, for which i followed this reference - https://github.com/apache/superset/issues/23622
This ran successfully on updating the upgrade function as mentioned in above link
Then ran - superset db init
Then started server using -
gunicorn -w 4 --worker-class gevent --worker-connections 1000 --timeout 1000 -b 127.0.0.1:8088 --limit-request-line 0 --limit-request-field_size 0 "superset.app:create_app()" --daemon --log-level DEBUG --log-file logs/superset.log --capture-output
Please help, i need to bring back dashboards asap.
GitHub link: https://github.com/apache/superset/discussions/33510
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
A maintainer has already been looped in.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=ae9883e3-e0b0-4ba9-8bba-a5736983120f) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191670
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
The error "No 'script_location' key found in configuration" indicates that the `alembic.ini` file is missing the `script_location` key, which specifies the location of the migration scripts. You need to add this key to your `alembic.ini` file. Here's how you can update your `alembic.ini` file:
1. Open your `alembic.ini` file.
2. Add the following line under the `[alembic]` section:
```ini
[alembic]
script_location = superset.migrations
```
This line tells Alembic where to find the migration scripts. Make sure the path `superset.migrations` correctly points to the directory containing your migration scripts. Once you've added this key, try running the Alembic command again.
Additionally, a maintainer has already been looped in to assist further with your issue.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/e2d71904-0d8d-4ebf-9dff-75d024c0436f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/e2d71904-0d8d-4ebf-9dff-75d024c0436f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/e2d71904-0d8d-4ebf-9dff-75d024c0436f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/e2d71904-0d8d-4ebf-9dff-75d024c0436f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e2d71904-0d8d-4ebf-9dff-75d024c0436f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/e2d71904-0d8d-4ebf-9dff-75d024c0436f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e2d71904-0d8d-4ebf-9dff-75d024c0436f?feedback_type=other)</sup>
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191574
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
To resolve the error "FAILED: No config file 'alembic.ini' found, or file has no '[alembic]' section," ensure that you have an `alembic.ini` file in your working directory. This file should contain a `[alembic]` section. You can use the following template for your `alembic.ini` file:
```ini
[alembic]
# template used to generate migration files
file_template = %%(year)d-%%(month).2d-%%(day).2d_%%(hour).2d-%%(minute).2d_%%(rev)s_%%(slug)s
# set to 'true' to run the environment during
# the 'revision' command, regardless of autogenerate
# revision_environment = false
# Logging configuration
[loggers]
keys = root,sqlalchemy,alembic,flask_migrate
[handlers]
keys = console
[formatters]
keys = generic
[logger_root]
level = WARN
handlers = console
qualname =
[logger_sqlalchemy]
level = WARN
handlers =
qualname = sqlalchemy.engine
[logger_alembic]
level = INFO
handlers =
qualname = alembic
[handler_console]
class = StreamHandler
args = (sys.stderr,)
level = NOTSET
formatter = generic
[formatter_generic]
format = %(levelname)-5.5s [%(name)s] %(message)s
datefmt = %H:%M:%S
[logger_flask_migrate]
level = DEBUG
handlers =
qualname = flask_migrate
```
Place this file in the directory where you are running the Alembic commands, and ensure it is correctly configured <sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/alembic.ini)</sup>.
Additionally, a maintainer has already been looped in to assist further with your issue.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/5b467d8f-4a72-47c5-93de-d8ddc28bfb6b?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/5b467d8f-4a72-47c5-93de-d8ddc28bfb6b?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/5b467d8f-4a72-47c5-93de-d8ddc28bfb6b?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/5b467d8f-4a72-47c5-93de-d8ddc28bfb6b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5b467d8f-4a72-47c5-93de-d8ddc28bfb6b?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/5b467d8f-4a72-47c5-93de-d8ddc28bfb6b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5b467d8f-4a72-47c5-93de-d8ddc28bfb6b?feedback_type=other)</sup>
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191402
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
@dosu Please connect me with some maintainer/admin to help with this
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191657
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
To resolve the `MySQLdb.OperationalError` related to the unknown column `slices.catalog_perm` after upgrading Apache Superset from version 4.0.0 to 4.1.2, you need to ensure that the database migrations have been applied correctly. This error indicates that the `catalog_perm` column is missing in the `slices` table, which should have been added by the migration script identified by the revision ID `58d051681a3b`.
Here are the steps you should follow:
1. **Re-run the Database Migrations**: Execute the following command to apply all pending migrations, including the one that adds the `catalog_perm` column to the `slices` table:
```bash
superset db upgrade
```
2. **Verify the Migration**: Ensure that the migration script `58d051681a3b` has been applied successfully. You can check the applied migrations in your database's `alembic_version` table.
3. **Restart the Superset Server**: After successfully applying the migrations, restart your Superset server to ensure all changes are loaded.
If you have already modified the upgrade function as per the GitHub issue you referenced, ensure that the changes are correct and that the migration script is not being skipped or altered in a way that prevents the `catalog_perm` column from being added.
If the issue persists, double-check the migration scripts and ensure that your database schema matches the expected structure for version 4.1.2 <sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/versions/2024-05-01_10-52_58d051681a3b_add_catalog_perm_to_tables.py)</sup>.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/05008a4d-9d64-4354-bad1-10bcf0713013?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/05008a4d-9d64-4354-bad1-10bcf0713013?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/05008a4d-9d64-4354-bad1-10bcf0713013?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/05008a4d-9d64-4354-bad1-10bcf0713013?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/05008a4d-9d64-4354-bad1-10bcf0713013?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/05008a4d-9d64-4354-bad1-10bcf0713013?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/05008a4d-9d64-4354-bad1-10bcf0713013?feedback_type=other)</sup>
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191040
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
The issue you're facing is due to the missing `catalog_perm` column in the `slices` and `tables` tables, which should have been added by the migration script with revision ID `58d051681a3b`. Since your `alembic_version` table shows `17fcea065655`, it indicates that the migration `58d051681a3b` has not been applied.
Here are the steps to resolve this:
1. **Check Migration Scripts**: Ensure that the migration script `58d051681a3b` is present in your Superset installation under the `superset/migrations/versions` directory. This script is responsible for adding the `catalog_perm` column to the `slices` and `tables` tables <sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/versions/2024-05-01_10-52_58d051681a3b_add_catalog_perm_to_tables.py)</sup>.
2. **Force Apply the Migration**: If the script is present, you can manually apply this specific migration by running:
```bash
alembic upgrade 58d051681a3b
```
This command will apply the migration that adds the `catalog_perm` column.
3. **Verify the Schema**: After applying the migration, check the schema of the `slices` and `tables` tables to ensure the `catalog_perm` column is present.
4. **Restart Superset**: Once the migration is applied, restart your Superset server to ensure all changes are reflected.
If the migration script is missing or if you encounter any issues while applying it, you may need to check your Superset installation for any discrepancies or reinstall the necessary migration scripts.
This is a tough nut to crack, could really use your help on this, @rusackas.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/3f7d73f0-d021-472e-870a-32d7f930cf20?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/3f7d73f0-d021-472e-870a-32d7f930cf20?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/3f7d73f0-d021-472e-870a-32d7f930cf20?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/3f7d73f0-d021-472e-870a-32d7f930cf20?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/3f7d73f0-d021-472e-870a-32d7f930cf20?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/3f7d73f0-d021-472e-870a-32d7f930cf20?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/3f7d73f0-d021-472e-870a-32d7f930cf20?feedback_type=other)</sup>
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191278
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
@dosu @rusackas In my packages i can see that this file exists -
2024-05-01_10-52_58d051681a3b_add_catalog_perm_to_tables.py
On running this cmd -
~/superset_venv/lib/python3.11/site-packages/superset/migrations/versions$ alembic upgrade 58d051681a3b
I am getting error:
FAILED: No config file 'alembic.ini' found, or file has no '[alembic]' section
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191366
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
To resolve the `MySQLdb.OperationalError` related to the unknown column `slices.catalog_perm` after upgrading Apache Superset from version 4.0.0 to 4.1.2, you need to ensure that the database migrations have been applied correctly. This error indicates that the `catalog_perm` column is missing in the `slices` table, which should have been added by the migration script identified by the revision ID `58d051681a3b`.
Here are the steps you should follow:
1. **Re-run the Database Migrations**: Execute the following command to apply all pending migrations, including the one that adds the `catalog_perm` column to the `slices` table:
```bash
superset db upgrade
```
2. **Verify the Migration**: Ensure that the migration script `58d051681a3b` has been applied successfully. You can check the applied migrations in your database's `alembic_version` table.
3. **Restart the Superset Server**: After successfully applying the migrations, restart your Superset server to ensure all changes are loaded.
If you have already modified the upgrade function as per the GitHub issue you referenced, ensure that the changes are correct and that the migration script is not being skipped or altered in a way that prevents the `catalog_perm` column from being added.
If the issue persists, double-check the migration scripts and ensure that your database schema matches the expected structure for version 4.1.2 <sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/versions/2024-05-01_10-52_58d051681a3b_add_catalog_perm_to_tables.py)</sup>.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=05008a4d-9d64-4354-bad1-10bcf0713013) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191040
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
@dosu I again ran superset db upgrade, there were no errors, following are the log lines printed:
/home/ubuntu/superset_venv/lib/python3.11/site-packages/celery/fixups/django.py:56: FixupWarning: Environment variable DJANGO_SETTINGS_MODULE is defined
but Django isn't installed. Won't apply Django fix-ups!
warnings.warn(FixupWarning(ERR_NOT_INSTALLED))
2025-05-19 08:50:40,454:INFO:superset.utils.screenshots:No PIL installation found
2025-05-19 08:50:40,876:INFO:superset.utils.pdf:No PIL installation found
WARNI [alembic.env] SQLite Database support for metadata databases will be removed in a future version of Superset.
INFO [alembic.env] Starting the migration scripts.
INFO [alembic.runtime.migration] Context impl SQLiteImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
INFO [alembic.env] Migration scripts completed. Duration: 00:00:00
I checked the schema of the following - tables and slices, and i dont see any catalog_perm column present there.
Output of alembic_version table is :
version_num: 17fcea065655
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191190
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
@dosu @rusackas In the migrations directory i see that file alembic.ini already exists, and is same as what you have shared.
On running this: ~/superset_venv/lib/python3.11/site-packages/superset/migrations$ alembic upgrade 58d051681a3b
Output: FAILED: No 'script_location' key found in configuration.
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191551
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
To resolve the error "FAILED: No config file 'alembic.ini' found, or file has no '[alembic]' section," ensure that you have an `alembic.ini` file in your working directory. This file should contain a `[alembic]` section. You can use the following template for your `alembic.ini` file:
```ini
[alembic]
# template used to generate migration files
file_template = %%(year)d-%%(month).2d-%%(day).2d_%%(hour).2d-%%(minute).2d_%%(rev)s_%%(slug)s
# set to 'true' to run the environment during
# the 'revision' command, regardless of autogenerate
# revision_environment = false
# Logging configuration
[loggers]
keys = root,sqlalchemy,alembic,flask_migrate
[handlers]
keys = console
[formatters]
keys = generic
[logger_root]
level = WARN
handlers = console
qualname =
[logger_sqlalchemy]
level = WARN
handlers =
qualname = sqlalchemy.engine
[logger_alembic]
level = INFO
handlers =
qualname = alembic
[handler_console]
class = StreamHandler
args = (sys.stderr,)
level = NOTSET
formatter = generic
[formatter_generic]
format = %(levelname)-5.5s [%(name)s] %(message)s
datefmt = %H:%M:%S
[logger_flask_migrate]
level = DEBUG
handlers =
qualname = flask_migrate
```
Place this file in the directory where you are running the Alembic commands, and ensure it is correctly configured <sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/alembic.ini)</sup>.
Additionally, a maintainer has already been looped in to assist further with your issue.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=5b467d8f-4a72-47c5-93de-d8ddc28bfb6b) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191402
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
The error "No 'script_location' key found in configuration" indicates that the `alembic.ini` file is missing the `script_location` key, which specifies the location of the migration scripts. You need to add this key to your `alembic.ini` file. Here's how you can update your `alembic.ini` file:
1. Open your `alembic.ini` file.
2. Add the following line under the `[alembic]` section:
```ini
[alembic]
script_location = superset.migrations
```
This line tells Alembic where to find the migration scripts. Make sure the path `superset.migrations` correctly points to the directory containing your migration scripts. Once you've added this key, try running the Alembic command again.
Additionally, a maintainer has already been looped in to assist further with your issue.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=e2d71904-0d8d-4ebf-9dff-75d024c0436f) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191574
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
Also i would like to add that i am usng sqlite database and not postgresql
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191223
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
@dosu Can someone from the team can be assigned to help me quickly on this?
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191201
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
@dosu Where is this alembic supposed to be present in my project and from it should be run.
I found this file in the migration directory in superset packages, and on running from there i am getting error.
I added this in my alembic.ini file:
script_location = /home/ubuntu/superset_venv/lib/python3.11/site-packages/superset/migrations
On running - alembic upgrade cmd from migrations directory got the error -
superset_venv) ubuntu@fcc-pricing-pg-superset:~/superset_venv/lib/python3.11/site-packages/superset/migrations$ alembic upgrade 58d051681a3b
Traceback (most recent call last):
File "/home/ubuntu/superset_venv/bin/alembic", line 8, in <module>
sys.exit(main())
^^^^^^
File "/home/ubuntu/superset_venv/lib/python3.11/site-packages/alembic/config.py", line 636, in main
CommandLine(prog=prog).main(argv=argv)
File "/home/ubuntu/superset_venv/lib/python3.11/site-packages/alembic/config.py", line 626, in main
self.run_cmd(cfg, options)
File "/home/ubuntu/superset_venv/lib/python3.11/site-packages/alembic/config.py", line 603, in run_cmd
fn(
File "/home/ubuntu/superset_venv/lib/python3.11/site-packages/alembic/command.py", line 406, in upgrade
script.run_env()
File "/home/ubuntu/superset_venv/lib/python3.11/site-packages/alembic/script/base.py", line 586, in run_env
util.load_python_file(self.dir, "env.py")
File "/home/ubuntu/superset_venv/lib/python3.11/site-packages/alembic/util/pyfiles.py", line 95, in load_python_file
module = load_module_py(module_id, path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_venv/lib/python3.11/site-packages/alembic/util/pyfiles.py", line 113, in load_module_py
spec.loader.exec_module(module) # type: ignore
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<frozen importlib._bootstrap_external>", line 940, in exec_module
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "/home/ubuntu/superset_venv/lib/python3.11/site-packages/superset/migrations/env.py", line 34, in <module>
if not current_app.config["ALEMBIC_SKIP_LOG_CONFIG"]:
^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_venv/lib/python3.11/site-packages/werkzeug/local.py", line 318, in _get_
obj = instance._get_current_object()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ubuntu/superset_venv/lib/python3.11/site-packages/werkzeug/local.py", line 519, in _get_current_object
raise RuntimeError(unbound_message) from None
RuntimeError: Working outside of application context.
This typically means that you attempted to use functionality that needed
the current application. To solve this, set up an application context
with app.app_context(). See the documentation for more information.
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191654
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
@dosu Can you tell the steps for downgrading from 4.1.2 to 4.0.0 with keeping my old db data. I can see that for this i need to run this sort of cmd: superset db downgrade <revision_id>
What revision_id is to be used?
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191703
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
@dosu How to resolve this?
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13190964
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
The issue you're facing is due to the missing `catalog_perm` column in the `slices` and `tables` tables, which should have been added by the migration script with revision ID `58d051681a3b`. Since your `alembic_version` table shows `17fcea065655`, it indicates that the migration `58d051681a3b` has not been applied.
Here are the steps to resolve this:
1. **Check Migration Scripts**: Ensure that the migration script `58d051681a3b` is present in your Superset installation under the `superset/migrations/versions` directory. This script is responsible for adding the `catalog_perm` column to the `slices` and `tables` tables <sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/versions/2024-05-01_10-52_58d051681a3b_add_catalog_perm_to_tables.py)</sup>.
2. **Force Apply the Migration**: If the script is present, you can manually apply this specific migration by running:
```bash
alembic upgrade 58d051681a3b
```
This command will apply the migration that adds the `catalog_perm` column.
3. **Verify the Schema**: After applying the migration, check the schema of the `slices` and `tables` tables to ensure the `catalog_perm` column is present.
4. **Restart Superset**: Once the migration is applied, restart your Superset server to ensure all changes are reflected.
If the migration script is missing or if you encounter any issues while applying it, you may need to check your Superset installation for any discrepancies or reinstall the necessary migration scripts.
This is a tough nut to crack, could really use your help on this, @rusackas.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=3f7d73f0-d021-472e-870a-32d7f930cf20) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191278
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "Nimishbansal-16 (via GitHub)" <gi...@apache.org>.
GitHub user Nimishbansal-16 added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
@rusackas Can you please assist here? I am not sure if i have to create the above files and what would its impact be
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191442
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
To downgrade from Superset version 4.1.2 to 4.0.0 while keeping your old database data, you need to use the `superset db downgrade` command with the appropriate revision ID. Unfortunately, I couldn't find the specific revision ID for version 4.0.0 in the repository. You may need to check the migration scripts in your Superset installation to identify the correct revision ID for version 4.0.0.
Here are the general steps for downgrading:
1. **Identify the Revision ID**: Look for the migration script corresponding to version 4.0.0 in the `superset/migrations/versions` directory. The revision ID is usually part of the filename.
2. **Run the Downgrade Command**: Once you have the correct revision ID, execute the following command:
```bash
superset db downgrade <revision_id>
```
3. **Verify the Downgrade**: Check your database schema to ensure it matches the expected structure for version 4.0.0.
4. **Restart Superset**: After downgrading, restart your Superset server to apply the changes.
Please ensure that you have backups of your database before performing the downgrade to prevent any data loss. If you encounter multiple head revisions, you may need to resolve migration conflicts by merging DB migrations as described in the Superset documentation <sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/versions/2015-09-21_17-30_4e6a06bad7a8_init.py)</sup><sup>[[2]](https://github.com/apache/superset/blob/master/docs/docs/contributing/development.mdx)</sup>.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/4b1fa04c-3167-4804-9229-6160a4412ff9?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/4b1fa04c-3167-4804-9229-6160a4412ff9?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/4b1fa04c-3167-4804-9229-6160a4412ff9?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/4b1fa04c-3167-4804-9229-6160a4412ff9?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4b1fa04c-3167-4804-9229-6160a4412ff9?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/4b1fa04c-3167-4804-9229-6160a4412ff9?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4b1fa04c-3167-4804-9229-6160a4412ff9?feedback_type=other)</sup>
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191736
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
A maintainer has already been looped in.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/ae9883e3-e0b0-4ba9-8bba-a5736983120f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ae9883e3-e0b0-4ba9-8bba-a5736983120f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ae9883e3-e0b0-4ba9-8bba-a5736983120f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ae9883e3-e0b0-4ba9-8bba-a5736983120f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ae9883e3-e0b0-4ba9-8bba-a5736983120f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/ae9883e3-e0b0-4ba9-8bba-a5736983120f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ae9883e3-e0b0-4ba9-8bba-a5736983120f?feedback_type=other)</sup>
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191670
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Unable to view dashboard post version upgrade from 4.0.0 to 4.1.2
<!-- Answer -->
To downgrade from Superset version 4.1.2 to 4.0.0 while keeping your old database data, you need to use the `superset db downgrade` command with the appropriate revision ID. Unfortunately, I couldn't find the specific revision ID for version 4.0.0 in the repository. You may need to check the migration scripts in your Superset installation to identify the correct revision ID for version 4.0.0.
Here are the general steps for downgrading:
1. **Identify the Revision ID**: Look for the migration script corresponding to version 4.0.0 in the `superset/migrations/versions` directory. The revision ID is usually part of the filename.
2. **Run the Downgrade Command**: Once you have the correct revision ID, execute the following command:
```bash
superset db downgrade <revision_id>
```
3. **Verify the Downgrade**: Check your database schema to ensure it matches the expected structure for version 4.0.0.
4. **Restart Superset**: After downgrading, restart your Superset server to apply the changes.
Please ensure that you have backups of your database before performing the downgrade to prevent any data loss. If you encounter multiple head revisions, you may need to resolve migration conflicts by merging DB migrations as described in the Superset documentation <sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/versions/2015-09-21_17-30_4e6a06bad7a8_init.py)</sup><sup>[[2]](https://github.com/apache/superset/blob/master/docs/docs/contributing/development.mdx)</sup>.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=4b1fa04c-3167-4804-9229-6160a4412ff9) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33510#discussioncomment-13191736
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org