Skip to content
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

Bulk-import Jpa-Server-Starter ID constraint error #5869

Open
Loiotile opened this issue Apr 23, 2024 · 1 comment
Open

Bulk-import Jpa-Server-Starter ID constraint error #5869

Loiotile opened this issue Apr 23, 2024 · 1 comment

Comments

@Loiotile
Copy link

Most of the times we try to run a bulk-import on our unsorted data (resources kept inside .ndjson files, with multiple references to eachother ids that need to be maintained), we encounter the following error: "ERROR c.u.f.c.BulkImportCommand HTTP 500 : Job is in FAILED state with 22 error count. Last error: Too many errors: 4. Last error msg was HAPI-0550: HAPI-0825: The operation has failed with a client-assigned ID constraint failure. This typically means that multiple client threads are trying to create a new resource with the same client-assigned ID at the same time, and this thread was chosen to be rejected. It can also happen when a request disables the Upsert Existence Check". This error doesn't occur for smaller groups of data; also, in rare occasions the program run with same settings and data causing this error can end up successful.
In our application.yaml have "autocreate_placeholder_reference_targets: true", in order to create placeholders for resources referenced before the resources themselves are actually populated, and we assumed that these placeholders could have been the reason behind the error.

  • HAPI FHIR Version 5
  • OS: Windows
  • Browser: Microsoft Edge

Additional context:
Use of hapi-fhir-CLI with localhost and PostgreSQL

@jkiddo
Copy link
Contributor

jkiddo commented Apr 28, 2024

I have the same observation when trying to do even small synthea-based imports running on H2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants