From 6a5c23c36b486ed0ad155e7ad28ae365549e8948 Mon Sep 17 00:00:00 2001 From: ianmarshall Date: Fri, 22 May 2020 13:45:17 -0400 Subject: [PATCH] Adding a proposed change log. --- ...863-enable-configuring-max-delete-conflicts-handled.yaml | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/5_1_0/1863-enable-configuring-max-delete-conflicts-handled.yaml diff --git a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/5_1_0/1863-enable-configuring-max-delete-conflicts-handled.yaml b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/5_1_0/1863-enable-configuring-max-delete-conflicts-handled.yaml new file mode 100644 index 00000000000..178dd56cd37 --- /dev/null +++ b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/5_1_0/1863-enable-configuring-max-delete-conflicts-handled.yaml @@ -0,0 +1,6 @@ +--- +type: fix +issue: 1863 +title: "Cascade deletes were failing in cases where the resource being deleted had more than 600 conflicts due to a hard-coded limit + on the number of conflicts that the CascadingDeleteInterceptor was allowed to process at a time. This hard-coded limit has been + replaced with an optional configuration parameter."