Open-EO / openeo-api

The openEO API specification
http://api.openeo.org
Apache License 2.0
93 stars 12 forks source link

Remove openeo:status from the "/jobs/{job_id}/results" collection response #497

Closed GeraldIr closed 1 year ago

GeraldIr commented 1 year ago

This field seems a bit redundant, as the value is gotten from a seperate API call to /jobs/{job_id} (which delivers metadata for a specific batch job), also it's only needed if the response is a STAC collection AND partial is true.

What is this actually being used for? It's not a huge inconvenience to update from 1.1.0 to 1.2.0 but it seems a bit strange.

I guess clarification would be nice.

m-mohr commented 1 year ago

It is an optional field (for now), so you can omit it if you want. The use case is that it can be important to know whether the job is complete (i.e. status = finished) or incomplete (i.e. status = canceled/error) in the metadata.

Related:

jdries commented 1 year ago

we actually use this field now to enable federated processing, so please don't remove it.

m-mohr commented 1 year ago

Yes, it was just recently added and is optional. So you don't need to implement it and there are good reasons in several use cases to keep it.