-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Use Case
When a recipe is sent to the cellPACK server in the body of the packing request, we want to add a firebase lookup step.
Probably branch off of feature/server-passed-recipe-json
Proposed Solution
This will look something like:
- When a user passes a recipe to the server in the body of the request, calculate that recipe's dedup_hash. We will use this dedup_hash as the ID in the
job_statuscollection instead of generating a UUID. - Check if this exact recipe already has an existing result in firebase by querying the
job_statuscollection for that dedup_hash. If so, retrieve that recipe's result file and return that to client - If the recipe doesn't exist in firebase yet, use the dedup_hash as the "job id" for this run (instead of generating a UUID), return it to the client, and run packing. Use this dedup_hash as the ID for the results posted to the
job_statuscollection on firebase.
We should now no longer have any concept of "job ID", we are instead using the dedup_hash in place of this. We should update the variable names to all say dedup_hash instead of job ID to avoid confusion. However, we still need to return "jobId" as a field in the response to the POST request to stay backwards compatible, we will work towards removing this once we're fully deployed.
The dedup_hash should also replace job ID in the path to the S3 outputs.
Metadata
Metadata
Assignees
Labels
No labels