Skip to content
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

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

Closed
GeraldIr opened this issue May 31, 2023 · 3 comments
Closed

Comments

@GeraldIr
Copy link
Member

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
Copy link
Member

m-mohr commented Jun 1, 2023

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
Copy link

jdries commented Aug 29, 2023

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

@m-mohr m-mohr closed this as not planned Won't fix, can't repro, duplicate, stale Aug 29, 2023
@m-mohr
Copy link
Member

m-mohr commented Aug 29, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants