You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "cphilibien (via GitHub)" <gi...@apache.org> on 2023/06/12 22:51:46 UTC
[GitHub] [superset] cphilibien opened a new issue, #24370: Superset upgrade issue: no such column: dbs.allow_multi_schema_metadata_fetch
cphilibien opened a new issue, #24370:
URL: https://github.com/apache/superset/issues/24370
After upgarde superset 2.0.0 to 2.1.0, I lost my databases connection
I had 2 database: 1 sqlite for superset's users and metadata and 1 BD postgres for my data.
The text error
```shell
An error occurred while fetching databases: (sqlite3.OperationalError) no such column: dbs.allow_multi_schema_metadata_fetch
[SQL: SELECT count(*) AS count_1
FROM (SELECT dbs.changed_on AS dbs_changed_on, dbs.id AS dbs_id, dbs.database_name AS dbs_database_name, dbs.sqlalchemy_uri AS dbs_sqlalchemy_uri, dbs.password AS dbs_password, dbs.expose_in_sqllab AS dbs_expose_in_sqllab, dbs.allow_run_async AS dbs_allow_run_async, dbs.allow_file_upload AS dbs_allow_file_upload, dbs.allow_ctas AS dbs_allow_ctas, dbs.allow_cvas AS dbs_allow_cvas, 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.created_by_fk AS dbs_created_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
FROM dbs LEFT OUTER JOIN ab_user AS created_by ON dbs.created_by_fk = created_by.id) AS anon_1]
(Background on this error at: http://sqlalche.me/e/13/e3q8)
```
#### How to reproduce the bug
I upgrade superset:
1. `pip install apache-superset --upgrade` => ok, you can see the version of superset
2. `superset db upgrade`
if I config SQLALCHEMY_DATABASE_URI with slqlite => upgrade stop at INFO [alembic.runtime.migration] Will assume transactional DDL.
scrrenshot:
if I config SQLALCHEMY_DATABASE_URI with postgres => upgrade show any errors
3. `superset init`
4. I connect to superset
if I config SQLALCHEMY_DATABASE_URI with slqlite => I have the error
if I config SQLALCHEMY_DATABASE_URI with postgres => my user login not working (logical)
I don't find solution to solve my issue, if someone can help with a tips or the solution, it could be appreciate
Thanks a lot!!!!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] cphilibien commented on issue #24370: Superset upgrade issue: no such column: dbs.allow_multi_schema_metadata_fetch
Posted by "cphilibien (via GitHub)" <gi...@apache.org>.
cphilibien commented on issue #24370:
URL: https://github.com/apache/superset/issues/24370#issuecomment-1588227293
I find my issue!!! it's was my python env
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Superset upgrade issue: no such column: dbs.allow_multi_schema_metadata_fetch [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #24370: Superset upgrade issue: no such column: dbs.allow_multi_schema_metadata_fetch
URL: https://github.com/apache/superset/issues/24370
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] cphilibien commented on issue #24370: Superset upgrade issue: no such column: dbs.allow_multi_schema_metadata_fetch
Posted by "cphilibien (via GitHub)" <gi...@apache.org>.
cphilibien commented on issue #24370:
URL: https://github.com/apache/superset/issues/24370#issuecomment-1597394516
I didn't active the good env and I install this version for sqlparse sqlparse=='0.4.3’
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Superset upgrade issue: no such column: dbs.allow_multi_schema_metadata_fetch [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #24370:
URL: https://github.com/apache/superset/issues/24370#issuecomment-1977339155
This version of Superset is no longer supported. If anyone is still encountering this in current versions (3.x) please open a new Issue or a PR to address the problem.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] franz3452 commented on issue #24370: Superset upgrade issue: no such column: dbs.allow_multi_schema_metadata_fetch
Posted by "franz3452 (via GitHub)" <gi...@apache.org>.
franz3452 commented on issue #24370:
URL: https://github.com/apache/superset/issues/24370#issuecomment-1596247324
> I find my issue!!! it's was my python env
Hello! I have the same problem. What was wrong with your env?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org