From 4fe7f6e322009bd48344be48b79714b1aa9e5f44 Mon Sep 17 00:00:00 2001 From: James Agnew Date: Tue, 21 Apr 2020 20:19:02 -0400 Subject: [PATCH] Update hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa/partitioning.md Co-Authored-By: Ken Stevens --- .../resources/ca/uhn/hapi/fhir/docs/server_jpa/partitioning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa/partitioning.md b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa/partitioning.md index e1e465dc9a5..8bbc6d2de2c 100644 --- a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa/partitioning.md +++ b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa/partitioning.md @@ -39,7 +39,7 @@ When partitioning is used, these two columns will be populated with the same val When a new resource is **created**, an [interceptor hook](#partition-interceptors) is invoked to request the partition ID and date to be assigned to the resource. -At the time that a resource is being **updated**, the partition ID and date from the previous version will be used. +When a resource is **updated**, the partition ID and date from the previous version will be used. When a **read operation** is being performed (e.g. a read, search, history, etc.), a separate [interceptor hook](#partition-interceptors) is invoked in order to determine whether the operation should target a specific partition. The outcome of this hook determines how the partitioning manifests itself to the end user: