Focused crawls are collections of frequently-updated webcrawl data from narrow (as opposed to broad or wide) web crawls, often focused on a single domain or subdomain.
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.
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
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:
The text was updated successfully, but these errors were encountered: