From 0a46d01fdcc6cd8134e048de0221a0f850ec8695 Mon Sep 17 00:00:00 2001 From: Jens Kristian Villadsen Date: Tue, 5 Aug 2025 10:23:07 +0200 Subject: [PATCH] Default back to not running with partitions --- src/main/resources/application.yaml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/src/main/resources/application.yaml b/src/main/resources/application.yaml index cff71e2..3623a04 100644 --- a/src/main/resources/application.yaml +++ b/src/main/resources/application.yaml @@ -244,22 +244,22 @@ hapi: ### Uncomment the following section, and any sub-properties you need in order to enable ### partitioning support on this server. - partitioning: - allow_references_across_partitions: false - partitioning_include_in_search_hashes: false - default_partition_id: 0 + #partitioning: + # allow_references_across_partitions: false + # partitioning_include_in_search_hashes: false + # default_partition_id: 0 ### Enable the following setting to enable Database Partitioning Mode ### See: https://hapifhir.io/hapi-fhir/docs/server_jpa_partitioning/db_partition_mode.html - database_partition_mode_enabled: true + # database_partition_mode_enabled: true ### Partition Style: Partitioning requires a partition interceptor which helps the server ### select which partition(s) should be accessed for a given request. You can supply your ### own interceptor (see https://hapifhir.io/hapi-fhir/docs/server_jpa_partitioning/partitioning.html#partition-interceptors ) ### but the following setting can also be used to use a built-in form. ### Patient ID Partitioning Mode uses the patient/subject ID to determine the partition - patient_id_partitioning_mode: true + # patient_id_partitioning_mode: true ### Request tenant mode can be used for a multi-tenancy setup where the request path is ### expected to have an additional path element, e.g. GET http://example.com/fhir/TENANT-ID/Patient/A - request_tenant_partitioning_mode: false + # request_tenant_partitioning_mode: false cors: allow_Credentials: true