FHIR icon indicating copy to clipboard operation
FHIR copied to clipboard

bulk data delete followed by status caused no output

Open d0roppe opened this issue 2 years ago • 3 comments

Describe the bug Issuing a Delete bulk data status on a job. then issuing a get bulk data status for the same job return code of 200, but no data in the response body just {}

Environment IBM FHIR Server - main

To Reproduce Issue a delete bulk data status of a job getting back a 202 code, then changing the call to a delete for the same job, it returned a 200 return code but the response body was empty except {}

Expected behavior If the status of a bulk data job returns a 200 return code it should have info in the response body.

d0roppe avatar Nov 23 '21 20:11 d0roppe

when a job is stopped, we don't return 202 when we restart it

Create an import

Stop the job curl --location --request PUT 'https://localhost:9443/ibm/api/batch/jobexecutions/406?action=stop'

curl --location --request GET 'https://localhost:9443/fhir-server/api/v4/$bulkdata-status?job=406'
--header 'X-FHIR-TENANT-ID: default'
--header 'Content-Type: application/fhir+json' {}

prb112 avatar Nov 23 '21 20:11 prb112

Not able to verify this issue. with a long running $export, and then issueing a Delete of that job, and then issuing a $bulkdata-status of that job, the status gets a 202, but it also seems to restart the job. And then when the job is done, I get a 500 error on the $bulkdata-status. If I issue delete job of a long running $export, and then issue the delete again. It actually stops and deletes the job. and then the $bulkdata-status call gets a 404 not found as expected when the job is done.

d0roppe avatar Feb 19 '22 17:02 d0roppe

We can debug - points to a different issue.

prb112 avatar Feb 19 '22 19:02 prb112