You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move the batch creation process of creating jobs and recipes to the messaging system for scalability.
Look at removing the usage (where possible) of the batch_job and batch_recipe models in favor of the job and recipe batch_id field. If possible, consider a plan to remove the batch_job and batch_recipe models.
The text was updated successfully, but these errors were encountered:
update_recipes - create job models that are ready, new recipes will create any jobs not already brought forward from superseded recipes, will now need to lock recipe models, punting on new recipe jobs pointing to superseded jobs because when doing recipe metrics will create one summary JSON field for recipe that holds metrics per job_name which will include superseded job IDs for use in creating new jobs
unpublish_jobs - new command message to perform job product unpublishing and superseding, make a comment in publish_job so that when we have multiple jobs per job_name, we appropriately unpublish/supersede products from superseded recipe when no direct superseded job link occurs
cancel_jobs - new command message to cancel jobs
process_recipe_input - new command message to process 100 recipes' input files, will send update_recipes messages
reprocess_recipes - new message that takes 100 recipes and supersedes them with new recipes, marks old recipe jobs as superseded, will need to create recipe_job models for jobs that are carried forward, sends process_recipe_input messages for new recipes and sends unpublish_jobs and cancel_jobs messages for superseded jobs
Update the batch creation logic to use the reprocess_recipes message.
The portion of the batch creation for new files will not be transitioned to use messaging. It will ultimately be replaced when batches are created from data sets.
Move the batch creation process of creating jobs and recipes to the messaging system for scalability.
Look at removing the usage (where possible) of the batch_job and batch_recipe models in favor of the job and recipe batch_id field. If possible, consider a plan to remove the batch_job and batch_recipe models.
The text was updated successfully, but these errors were encountered: