The Wayback Machine - https://web.archive.org/web/20220113001405/https://github.com/apache/superset/issues/17991
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flask-Migrate output is not logged during alembic migrations #17991

Open
nytai opened this issue Jan 11, 2022 · 1 comment
Open

Flask-Migrate output is not logged during alembic migrations #17991

nytai opened this issue Jan 11, 2022 · 1 comment

Comments

@nytai
Copy link
Member

@nytai nytai commented Jan 11, 2022

Due to the changes mentioned here miguelgrinberg/Flask-Migrate#384 the output of flask_migrate is not being logged during alembic migrations. Looks like the alembic.ini file needs to be updated to include logging config for flask_migrate.

These changes should work:

[loggers]
keys = root,sqlalchemy,alembic,flask_migrate

...

[logger_flask_migrate]
level = DEBUG
handlers =
qualname = flask_migrate

...
@jayakrishnankk
Copy link
Contributor

@jayakrishnankk jayakrishnankk commented Jan 11, 2022

Is this in master branch? I am able to see the migration runs while I run superset db upgrade from master branch (git hash=46715b295), without this additional configuration.

For example:

....
INFO  [alembic.runtime.migration] Running upgrade 3ba29ecbaac5 -> fe23025b9441, rename_big_viz_total_form_data_fields
INFO  [alembic.runtime.migration] Running upgrade fe23025b9441 -> 31bb738bd1d2, move_pivot_table_v2_legacy_order_by_to_timeseries_limit_metric
INFO  [alembic.runtime.migration] Running upgrade 31bb738bd1d2 -> bb38f40aa3ff, Add force_screenshot to alerts/reports

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants