Skip to content

Fix: passing empty request details for bulk-export#1

Open
GoodOliver wants to merge 1 commit intomasterfrom
fix/bulk-export-with-partitioning
Open

Fix: passing empty request details for bulk-export#1
GoodOliver wants to merge 1 commit intomasterfrom
fix/bulk-export-with-partitioning

Conversation

@GoodOliver
Copy link

@GoodOliver GoodOliver commented May 28, 2025

Background

When running a bulk‐export ($export) against a partitioned HAPI FHIR server, the export job fails in the “write to binaries” step with:

HAPI-1319: No interceptor provided a value for pointcut: STORAGE_PARTITION_IDENTIFY_READ and STORAGE_PARTITION_IDENTIFY_ANY

Root cause: the collision‐check and final binaryDao.update(...) calls in NdJsonResourceWriter use a brand‐new SystemRequestDetails() (with no partition info), so the partition‐identification interceptor can’t resolve which tenant to read/write under.

Updates

In NdJsonResourceWriter.accept(...):

  1. Replace the new SystemRequestDetails() with the request details with partition information.

  2. Use that same SystemRequestDetails instance for both:

  • The binaryDao.read(idElement, srd, true) collision check
  • The binaryDao.update(binary, srd) write operation

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

Successfully merging this pull request may close these issues.

1 participant