From 015502e98ef3a346efc99f5146d176faee4e2c8d Mon Sep 17 00:00:00 2001 From: jamesagnew Date: Mon, 30 Nov 2020 18:59:53 -0500 Subject: [PATCH] Docs tweak --- .../uhn/hapi/fhir/docs/server_jpa_partitioning/partitioning.md | 1 - 1 file changed, 1 deletion(-) diff --git a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_partitioning/partitioning.md b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_partitioning/partitioning.md index 395dfca3b81..1dc74cdbad7 100644 --- a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_partitioning/partitioning.md +++ b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_partitioning/partitioning.md @@ -80,7 +80,6 @@ The criteria for determining the partition will depend on your use case. For exa A hook against the [`Pointcut.STORAGE_PARTITION_IDENTIFY_READ`](/hapi-fhir/apidocs/hapi-fhir-base/ca/uhn/fhir/interceptor/api/Pointcut.html#STORAGE_PARTITION_IDENTIFY_READ) pointcut must be registered, and this hook method will be invoked every time a resource is created in order to determine the partition to assign the resource to. - As of HAPI FHIR 5.3.0, the *Identify Partition for Read* hook method may return multiple partition names or IDs. If more than one partition is identified, the server will search in all identified partitions. ## Examples