-
Notifications
You must be signed in to change notification settings - Fork 0
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
feature request: endpoint to delete a batch job entry #19
Comments
In which case is the client executing the DELETE request? If you are using the data in ES for reporting purposes or post-mortems, it makes sense to not delete the document but to mark it as deleted and hide it from the listings. |
On the level of the openEO API, users can delete batch jobs, which:
But indeed, on the level of job registry I would keep the metadata (for reporting/post-mortem reasons) and just flag the document as deleted, so that we can properly hide the job entry from a regular user's batch job listing. I'd propose to add an optional toplevel field "deleted" which:
@JanssenBrm I'm not sure if this elegantly allows to write an ES query to only select docs where this field is missing/null? |
As the query is sent in the request body, we can always extend it on the backend to always include an additional filter for these hidden jobs. |
yes I understand, |
These kinds of queries are indeed supported in ES. If we make sure that only the backend can manipulate the |
API needs support for
DELETE /jobs/{id}
, which should deletes the whole document related to the batch job.To be discussed when this feature request is to be started:
should we actually delete the whole document, or just flag it as deleted in some way and hide it from default listings? Keeping some metadata about batch jobs might be important for reporting, usage tracking, post-mortem investigations, etc
(not high prio)
The text was updated successfully, but these errors were encountered: