opengeospatial / opengeospatial/ogcapi-processes
Part 4: Clarify that default execution mode is at discretion of backend
Nobody has claimed this yet.
- Dominant language
- AsciiDoc
- Stars
- 63
- Forks
- 46
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Can the backend decide what the default execution mode is? So there not really any negotiation to get "created" in openEO, which is because there might be operations that you may want to run before actually starting the computation (e.g. estimating the costs).
In openEO it's certainly async, and for OAP it seems sync (which is a bit counterintuitive for me, but that might be because we call jobs actually batch jobs in openEO and batch jobs in synchronous mode feel wrong).
Originally posted by @m-mohr in https://github.com/opengeospatial/ogcapi-processes/pull/437#discussion_r1792670766
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion quoted from pull request #437 and review the specification text governing the default execution mode. Clarify whether the backend may choose the default mode and ensure the resulting wording reflects the intended distinction between synchronous and asynchronous execution.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100