Details
-
Type:
Bug
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ap_verify
-
Labels:None
-
Story Points:6
-
Epic Link:
-
Sprint:AP F18-1, AP F18-3, AP F18-4
-
Team:Alert Production
Description
ap_verify tests whether particular types of data have been ingested, and only attempts ingestion if they have not. However, the checks currently address whether ingestion began, not whether it finished successfully. This may cause problems if ingestion fails partway through, or if the order in which datasets are ingested is changed during future refactoring.
Either the ingestion checks need to be rewritten to directly test ingestion completion, or IngestTask needs better handling of duplicate files.
After spending some time thinking about this, I'm closing the issue as Won't Fix. The circumstances in which the bug would actually appear are fairly unlikely (the user needs to interrupt or fail to ingest a dataset, then try to start over without clearing out the repositories), and every solution I can think of would cause more substantial problems: