Filter out non-requested outputs #380
Labels
project/OGC
Related to OGC testbeds or relavant projects.
triage/conformance
Issue related to fixing/ensuring compliance to specifications.
triage/feature
New requested feature.
Milestone
Description
In contrast to #375, if not all outputs are provided, the results should report only requested ones.
This impacts mostly when
response: raw
is requested (see #376), since it can make the difference between multipart output vs single output. Furthermore, the response the size can be reduced as well.In terms of processing execution,
Weaver
will not omit the creation and storage of those outputs (too complicated consideringCWL
App Package abstraction), but the job status response could report them partially as requested.outputs
as requested/jobs/{jobID}/outputs/{outputID}
retrieval anyway? Support/results/{id}
and/outputs/{id}
routes #18outputs: {}
indicates no-output?
), then the operation is allowedoutputs
is equivalent to requesting all outputstodo
in https://github.com/crim-ca/weaver/blob/master/docs/source/processes.rst#execution-bodyReferences
The text was updated successfully, but these errors were encountered: