Closed ynaim94 closed 2 years ago
Initial questions on the QA:
Promoting from backup
arthur.py promote_schemas --from-position backup mock_arthur_schema ... 2022-06-22 16:46:07 - INFO - Promoting 1 schema(s) from backup position: 'mock_arthur_schema' 2022-06-22 16:46:07 - INFO - Renaming schema 'mock_arthur_schema' from 'etl_backup$mock_arthur_schema' ...
-- Table was promoted SELECT * FROM mock_arthur_schema.table;
a_column constant
Did this succeed because of the prior arthur.py promote_schemas --from-position staging mock_arthur_schema
command?
Recreating table in backup
arthur.py promote_schemas --from-position staging mock_arthur_schema
SELECT * FROM etl_backup$mock_arthur_schema.table;
a_column constant
Given that you previously ran arthur.py promote_schemas --from-position staging mock_arthur_schema --no-backup
, did you need to also run arthur.py upgrade --with-staging mock_arthur_schema
before running this?
Description
Adding flag to not backup loaded data when promoting staging data. This allow us to temporarily save disk space.
QA
Creating table in staging
Promoting from staging
Recreating table in staging
Promoting from staging with no backup
Promoting from backup
Recreating table in staging
Recreating table in backup
Promoting from backup with no-backup flag (The flag has no effect here)