-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support adding additional parameters to jobs, services etc. #125
Comments
Are there any known workarounds to inject custom job_options in the POST data of For example, when using it with the VITO/CDSE back-ends users sometimes want to increase memory limits (e.g. |
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.
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. |
Makes sense indeed. |
Do you take over adding/proposing it for SAP10? @soxofaan |
I added it to the "table topics" spreadsheet. |
Good. I could work on it in collaboration with Edzer and Florian (for release), I think. |
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
The text was updated successfully, but these errors were encountered: