-
Notifications
You must be signed in to change notification settings - Fork 10
Celery : introduce a "collection_jobs" table for job tracking #389
Description
Problem in hand -
Currently we have two background job functions in our collection module, which are collection creation and collection deletion, since both of them can take take their getting finished. Now we have status and error message column for the creation of collection but we do not have it for deletiong of collection, so if a collection deletion job fails, we have no records of it other than logs. this is not very trackable and scalable because let us say we want to do cleanup of failed deletion once more, we have no proper record of deletion jobs which failed .
Proposed solution -
The collection creation job's status and error message will no longer be stored in the collection table but will instead be moved to the "collection_jobs" table. The collection object itself will only be created in the collection table after the job has been successfully completed. So create collection endpoint will give back a collection job id, else if it is a failed job, that stays in the job table with the status and error message.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status