genome / ptero-workflow

Client-facing API for the PTero system
1 stars 6 forks source link

Stop storing job parameters #250

Open davidlmorton opened 8 years ago

davidlmorton commented 8 years ago

Job parameters are stored in the workflow DB as well as submitted and stored in the Job service's DB. The plan is to persist only the job's ID and a token the job service provides upon submission. This token will be used to trigger the job to run.

Along with the 'run_token', the workflow service will submit additional 'runtime_environment' so that the job can phone home to get inputs and whatnot.

davidlmorton commented 8 years ago

Another option would be to make the parameters column nullable and delete the parameters after successfully submitting to the job service. The advantage of this option is that it is easier to implement (it only involves changes to the workflow service). The disadvantage is that it doesn't provide early job parameter validation.