Fix bug when trying to get job result in binary format #1798
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Currently, none of the existing process managers (TinyDB, MongoDB, PostgreSQL) is able to return binary process outputs on a GET request to
/jobs/<job-id>/results
(get_job_result
method of the managers).This is especially problematic for asynchronous processes as there seems to be no way to actually get the process outputs. For synchronous process calls, binary data can already be returned on POST requests to
/processes/<process-id>/execution
(see).This PR should solve the issue for all three aforementioned managers.
Related Issue / discussion
Additional information
Dependency policy (RFC2)
Updates to public demo
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)