Support adding additional parameters to jobs, services etc.
m-mohr opened this issue · comments
Support the additional parameters in create_job, create_service etc.
This could then be used to add e.g. the job_options parameter as used by VITO.
Unfortunately, the ... parameter in the functions is already used to pass things through to the JSON library. So either er want to split the data depending on whether the parameter is known by the JSON library, and otherwise pass it in the body. Or we add an additional paramater as proposed in the client dev guide and implemented also in the JS client.
Related issue: Open-EO/openeo-api#276
Related forum topic: https://discuss.eodc.eu/t/error-loading-sentinel-3-slstr/395/6
Are there any known workarounds to inject custom job_options in the POST data of create_job?
For example, when using it with the VITO/CDSE back-ends users sometimes want to increase memory limits (e.g. executor-memory), which does not seem possible with the current openEO R client package.
Not that I'm aware of, just checked the code again, but I don't think there's a way right now to add additional parameters.
Shouldn't be difficult to add though.
- I assume, ~4 hours implementation
- some hours for a re-release, could be combined with the v2 process changes changes in SAP10, I think
Maybe something we could try to add to openEO Platform SAP10? @soxofaan
@flahn are you the only person who can release on CRAN?
@m-mohr I couldn't find anything specific about who can send in packages at CRAN. Might be that all authors can, but I'm not sure. But if there is a new version to be released, I can definitely take care of running checks and the submission to CRAN.
Maybe something we could try to add to openEO Platform SAP10? @soxofaan
Makes sense indeed.
Do you take over adding/proposing it for SAP10? @soxofaan
I added it to the "table topics" spreadsheet.
But to clarify: I don't think that VITO would be able to work on the implementation (we don't have people with enough R experience to do this in just 4 man hours, especially because it involves being careful about backward/forward compatibility )
Good. I could work on it in collaboration with Edzer and Florian (for release), I think.