From fb4e620ba81d992fdc394842fba276961cb1f9fa Mon Sep 17 00:00:00 2001 From: James Agnew Date: Tue, 21 Apr 2020 20:19:50 -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 d356b762d4a..5204114acb1 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 @@ -44,7 +44,7 @@ When a resource is **updated**, the partition ID and date from the previous vers 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: * The system can be configured to operate as a **multitenant** solution by configuring the partition interceptor to scope all read operations to read data only from the partition that request has access to.``` -* If read operations are scopes to all partitions, then the partitioning is simply partitioning the data into logical segments. +* The system can be configured to operate with logical segments by configuring the partition interceptor to scope read operations to access all partitions. # Enabling Partitioning in HAPI FHIR