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
Uploading Resources by POST ,forces the Hapi fhir server to strictly create New Resources and generates a new internal Resource ID.
This leads to data duplication in case the same resource is POSTed more than Once .
When handling Referential Integrity ,Hapi generates new dummy resources which continuously leads to unnecessary data duplication .
see Talk Post for more details.
This should be implemented both in Streaming and Batch modes.
The text was updated successfully, but these errors were encountered:
bashir2
added
bug
Something isn't working
P1:must
As issue that definitely needs to be implemented in near future.
labels
Jan 28, 2021
Thanks @mozzy11 for catching this issue; I am marking this as a "bug" since this is a regression and the original intention was to keep the resource IDs. I am not sure if there is any case where we would need POST instead of PUT because of the broken referential integrity issue but adding @pmanko to make sure this behavior is okay with his use-case.
Uploading Resources by POST ,forces the Hapi fhir server to strictly create New Resources and generates a new internal Resource ID.
This leads to data duplication in case the same resource is POSTed more than Once .
When handling Referential Integrity ,Hapi generates new dummy resources which continuously leads to unnecessary data duplication .
see Talk Post for more details.
This should be implemented both in Streaming and Batch modes.
The text was updated successfully, but these errors were encountered: