You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/04/06 19:24:29 UTC
[GitHub] [superset] betodealmeida commented on pull request #19543: fix(migrations): reorder skipped 1.4 migrations
betodealmeida commented on PR #19543:
URL: https://github.com/apache/superset/pull/19543#issuecomment-1090673944
I'm running `superset db upgrade` and master right now, with a clean DB, and no migrations are applied:
```
% psql master
psql (14.2)
Type "help" for help.
master=# \dt
List of relations
Schema | Name | Type | Owner
--------+-------------------------+-------+-------
public | ab_permission | table | beto
public | ab_permission_view | table | beto
public | ab_permission_view_role | table | beto
public | ab_register_user | table | beto
public | ab_role | table | beto
public | ab_user | table | beto
public | ab_user_role | table | beto
public | ab_view_menu | table | beto
(8 rows)
master=#
```
Nothing happens on `superset db upgrade`:
```
% superset db upgrade
Loaded your LOCAL configuration at [/Users/beto/Projects/incubator-superset/superset_config.py]
--------------------------------------------------------------------------------
WARNING
--------------------------------------------------------------------------------
A Default SECRET_KEY was detected, please use superset_config.py to override it.
Use a strong complex alphanumeric string and use a tool to help you generate
a sufficiently random sequence, ex: openssl rand -base64 42
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
logging was configured successfully
2022-04-06 12:24:03,523:INFO:superset.utils.logging_configurator:logging was configured successfully
2022-04-06 12:24:03,536:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-04-06 12:24:03,542:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-04-06 12:24:03,548:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
```
--
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