Clean Up Duplicated Azure Storage tables for HlaMetadata
benbelow opened this issue · comments
Currently regenerating the HMD creates a fresh storage table which never gets cleaned up. Older tables for same version of the HMD should be removed via a manually trigger clean up function; only those tables listed in the reference table should be kept.
Example of how it could be done in code (as it is not possible to delete multiple tables at once via Storage Explorer):https://stackoverflow.com/questions/29825208/remove-all-tables-in-azure-table-storage
We may also want to extend this to allow cleaning up of older nomenclature versions - perhaps we could add a configurable value to allow any installation of Atlas to only keep the x
most recent nomenclature versions in its HMD?
This might be quite risky for installations using Match Prediction, as new HF sets are expected to be infrequently generated, meaning we'll have some quite out of date nomenclature used in HF sets.