You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using bulk export service on Docker with the hapiproject/hapi:latest image. And after setting up all the bulk service configurations, it can work perfectly in my container. But after four days, I startup the hapi fhir container, the patient/$export request could not export any data in hapi. The resources are still inside the server, and hapi do generate bulk export jobs successfully, but there are no resources been exported. I’m wondering whether this is a bug or not.
Here are my logs, thank you for your patience.
First time using bulk export, it generates three binary resources(patient, observation, condition).
Hello team,
I've been using bulk export service on Docker with the
hapiproject/hapi:latest
image. And after setting up all the bulk service configurations, it can work perfectly in my container. But after four days, I startup the hapi fhir container, the patient/$export request could not export any data in hapi. The resources are still inside the server, and hapi do generate bulk export jobs successfully, but there are no resources been exported. I’m wondering whether this is a bug or not.Here are my logs, thank you for your patience.
First time using bulk export, it generates three binary resources(patient, observation, condition).
First time using bulk export log.txt
The deleting bulk export job generates after startup
Deleting bulk export job generates after startup log.txt
Second time using bulk export, it doesn’t generate any binary resources.
Second time using bulk export.txt
The text was updated successfully, but these errors were encountered: