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
Describe the bug
When $expunge requests are made with the expungeDeletedResources parameter set to true, we also call JpaResourceExpungeService.deleteAllSearchParams. However, search parameters should have already been deleted when the resource itself was deleted. This unnecessary query has lead to tangible performance issues.
To Reproduce
Load some resources.
Submit a DELETE request to mark some of the resources as deleted.
POST an $expunge request with "expungeDeletedResources" parameter set to true.
The $expunge request results in a call to JpaResourceExpungeService.deleteAllSearchParams, as can be observed with a breakpoint.
Expected behavior
$expunge does not call JpaResourceExpungeService.deleteAllSearchParams.
Environment (please complete the following information):
HAPI FHIR Version: 7.3.0-SNAPSHOT
The text was updated successfully, but these errors were encountered:
Describe the bug
When
$expunge
requests are made with theexpungeDeletedResources
parameter set to true, we also callJpaResourceExpungeService.deleteAllSearchParams
. However, search parameters should have already been deleted when the resource itself was deleted. This unnecessary query has lead to tangible performance issues.To Reproduce
The $expunge request results in a call to
JpaResourceExpungeService.deleteAllSearchParams
, as can be observed with a breakpoint.Expected behavior
$expunge does not call
JpaResourceExpungeService.deleteAllSearchParams
.Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: