[GitHub] [superset] jayakrishnankk commented on issue #17991: Flask-Migrate output is not logged during alembic migrations

[GitBox <gi...@apache.org>]

jayakrishnankk commented on issue #17991:
URL: https://github.com/apache/superset/issues/17991#issuecomment-1010196550


   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
   
   ```


-- 
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