Stream: bulk data
Topic: NDJson lifetime in Kickoff Request
Jacob Abraham (Sep 10 2020 at 17:56):
Is there a way to define the expiry of generated ndjson files during the kickoff request?
Josh Mandel (Sep 10 2020 at 18:15):
No -- right now, file retention is a server responsibility, and clients can provide an "ok to delete now" hint by calling DELETE.
Josh Mandel (Sep 10 2020 at 18:16):
It's hard for a client to specify a time because the time required would depend on the size of the export (as well as the client + server network bandwidth), which are factors outside the client's control and unknown at kick-off time.
Jacob Abraham (Sep 10 2020 at 18:34):
Yeah, it does make sense as the persistence is maintained by the server and client does not have much idea about it. But if the lifetime of the resource was defined in the manifest, atleast the client would know how long it would last and if the client is taking more time , then it can refresh or restart the job.
Dan Gottlieb (Sep 10 2020 at 18:37):
Per Vlad's point on our Zoom discussion, the server can set a Expires header on the complete response to indicate when it will be removing the files: http://build.fhir.org/ig/HL7/bulk-data/export/index.html#response---complete-status
Last updated: Apr 12 2022 at 19:14 UTC
