Batch submit jobs through API (Swagger)
On Terra, the job submission page allows one to select multiple samples in a batch (a sample set is formed automatically in that case), and the jobs history will show one submission, in which there's one entry for each sample being processed.
On FISS, this feature looks to be approximated by its API `create_submission`, which in turn makes API call to
Consider the scenario where one wants to do advanced filtering on the samples to process, which isn't possible yet on Terra GUI but possible with FISS, and then submit a batch job with the selected samples, which is possible with Terra GUI, but unclear how with FISS.
As I study the API, the magic may be in `expression`, whose documentation reads
Expression that resolves to one or more entities matching the entity type in the method configuration. Optional if the method configuration has no root entity.
I'd guess the Terra GUI's "batch submission" works through this magic `expression`. So I'm interested in seeing an example of that.
Or if not, I'm interested in learning however Terra cleverly resolves "batch submission" issue.
Hi Steve Huang,
Thanks for writing in. We'll take a look at your question and get back to you as soon as we can.
Hi Steve Huang,
Sorry for the delayed response. I asked our engineers about this, and unfortunately, it sounds like the
expressionparameter does not work in the way you are hoping.
Expressionis for traversing from the submitted entity/entities to the root entity/entities to launch workflows against.
Please let me know if you have any questions.
Thanks for the reply!
So it's not the 'magic' `expression`. Then how should be submit jobs in batch mode, through an API call? Currently we do so by looping over the entities that need to be analyzed, which results in one submission per entity.
In the end, we aim to achieve something similar to the following with the Terra GUI: select multiple entities from a table, and submit them as a `set` for analysis, but each entity will be processed through the WDL workflow independently.
Please sign in to leave a comment.