@@ -190,7 +190,9 @@ hapi:
190
190
# default_encoding: JSON
191
191
# default_pretty_print: true
192
192
# default_page_size: 20
193
+ # delete_enabled: true
193
194
# delete_expunge_enabled: true
195
+ # match_url_cache_enabled: false
194
196
# enable_repository_validating_interceptor: true
195
197
# enable_index_missing_fields: false
196
198
# enable_index_of_type: true
@@ -237,24 +239,24 @@ hapi:
237
239
- http://loinc.org/*
238
240
- https://loinc.org/*
239
241
240
- # # ## Uncomment the following section, and any sub-properties you need in order to enable
241
- # # ## partitioning support on this server.
242
- # partitioning:
243
- # allow_references_across_partitions: false
244
- # partitioning_include_in_search_hashes: false
245
- # default_partition_id: 0
246
- # ### Enable the following setting to enable Database Partitioning Mode
247
- # ### See: https://hapifhir.io/hapi-fhir/docs/server_jpa_partitioning/db_partition_mode.html
248
- # database_partition_mode_enabled: false
249
- # ### Partition Style: Partitioning requires a partition interceptor which helps the server
250
- # ### select which partition(s) should be accessed for a given request. You can supply your
251
- # ### own interceptor (see https://hapifhir.io/hapi-fhir/docs/server_jpa_partitioning/partitioning.html#partition-interceptors )
252
- # ### but the following setting can also be used to use a built-in form.
253
- # ### Patient ID Partitioning Mode uses the patient/subject ID to determine the partition
254
- # patient_id_partitioning_mode: false
255
- # ### Request tenant mode can be used for a multi-tenancy setup where the request path is
256
- # ### expected to have an additional path element, e.g. GET http://example.com/fhir/TENANT-ID/Patient/A
257
- # request_tenant_partitioning_mode: false
242
+ # ## Uncomment the following section, and any sub-properties you need in order to enable
243
+ # ## partitioning support on this server.
244
+ partitioning :
245
+ allow_references_across_partitions : false
246
+ partitioning_include_in_search_hashes : false
247
+ default_partition_id : 0
248
+ # ## Enable the following setting to enable Database Partitioning Mode
249
+ # ## See: https://hapifhir.io/hapi-fhir/docs/server_jpa_partitioning/db_partition_mode.html
250
+ database_partition_mode_enabled : true
251
+ # ## Partition Style: Partitioning requires a partition interceptor which helps the server
252
+ # ## select which partition(s) should be accessed for a given request. You can supply your
253
+ # ## own interceptor (see https://hapifhir.io/hapi-fhir/docs/server_jpa_partitioning/partitioning.html#partition-interceptors )
254
+ # ## but the following setting can also be used to use a built-in form.
255
+ # ## Patient ID Partitioning Mode uses the patient/subject ID to determine the partition
256
+ patient_id_partitioning_mode : true
257
+ # ## Request tenant mode can be used for a multi-tenancy setup where the request path is
258
+ # ## expected to have an additional path element, e.g. GET http://example.com/fhir/TENANT-ID/Patient/A
259
+ request_tenant_partitioning_mode : false
258
260
259
261
cors :
260
262
allow_Credentials : true
0 commit comments